Fix handling of DEFAULT ACLs in the restore dialog
Fix a couple more wx2.9 related assertions.
Fix the reverse-engineered SQL of an operator

Per report from Bartosz Dmytrak.
Revert "Fix another issue related to wxWidgets 2.9"

This reverts commit 4e8c217f812a0ecc95a02db367d8af63f39073ad.

All displayed numbers were wrong.
Fix another wxWidgets 2.9 assert

Report from Colin Beckingham
Make sure you can right-click on the right of the name

Requested by Dave.
Get rid of short table names in DD
Fix deleting lines in frmEditGrid with 64bit systems

I believe I've fixed a problem where pgAdmin intermittently crashes on
64 bit systems while deleting rows.  The issues seems to be that, among
other things, sqlTable::DeleteRows() in frm/frmEditGrid.cpp attempts to
remove an element in lineIndex by shifting down the remaining elements.
Unfortunately the "sizeof" is taking the size of the wrong thing.

I suspect this is only an issue on systems where pointers and "int"s are
different sizes, which should be 64 bit systems, but I have only have a
64 bit Linux system handy to try.

Increasing the number of rows that follow the row deleted should
increase the probability of getting a crash, but Valgrind always
complains about bad reads and writes for the memmove() in question.

Steps to reproduce the problem:
1) Choose a table that has roughly 200 or more rows.  Here's a dump of
   such a table:
   http://selliott.org/pgadmin/table-200-rows.sql
2) Navigate to the "Edit Data" window (the window navigated to by
   selecting the View Data / View All Rows for the table in question).
3) Select a low numbered row, such as the fifth row.
4) Right click and select "Delete".  The crash may happen when the
   delete is confirmed after the subsequent dialog.
Drop autovacuum ANALYZE parameters for TOAST tables

autovacuum doesn't have any ANALYZE parameters for TOAST tables.

Per report from Bartosz Dmytrak.
Fix the reverse-engineered SQL for SQL/MED server

Per report from Bartosz Dmytrak.
Fix index population, per report from Timon.
Fix the SQL when adding a new index without a name

When a user adds an index without setting its name, but with a comment or the
CLUSTER option, the two specific SQL commands to set the comment and the
CLUSTER option don't have the name of the index (as we don't know it yet), and
thus fail.

If we don't have a name, we now disable both widgets (comment and cluster),
and we don't take care of their value in GetSql method().

Per report from Bartosz Dmytrak
Support for the new two columns in 9.2 pg_stat_database

block_read_time, and block_write_time
Fix a 2.9 issue with dlgForeignKey

Report by Colin Beckingham
Move references table textbox to the third tab of dlgForeignKey

Per request from Colin Beckingham.
Fix server reconnect option when the browser becomes disconnected from the server.
Ensure we track the dialogue in the correct object when opening
properties dialogues.
Use an enum for tabs instead of real numbers

I always forget to fix the number of the deleted page when I add a new tab in dlgTable. This will hopefully fix this issue.
Fix handling of parameter handling for edbspl functions and package procedures/functions.
Fix RE of options in foreign tables

Report from Regina.