Author: hiroshi
Date: 2007-10-04 17:01:49 +0100 (Thu, 04 Oct 2007)
New Revision: 6713
Revision summary: http://svn.pgadmin.org/cgi-bin/viewcvs.cgi/?rev=6713&view=rev
Log:
Ooops,mistake of a refix date...
Modified:
trunk/pgadmin3/CHANGELOG
---(end of broadcast)
Author: hiroshi
Date: 2007-10-04 17:00:30 +0100 (Thu, 04 Oct 2007)
New Revision: 6712
Revision summary: http://svn.pgadmin.org/cgi-bin/viewcvs.cgi/?rev=6712&view=rev
Log:
Fixed new VIEW creation conditions.
Modified:
branches/REL-1_6_0_PATCHES/pgadmin3/CHANGELOG
branches/REL-1_6_0_PATC
Author: hiroshi
Date: 2007-10-04 15:38:40 +0100 (Thu, 04 Oct 2007)
New Revision: 6711
Revision summary: http://svn.pgadmin.org/cgi-bin/viewcvs.cgi/?rev=6711&view=rev
Log:
Fixed new VIEW creation conditions.
Modified:
trunk/pgadmin3/CHANGELOG
trunk/pgadmin3/pgadmin/dlg/dlgView.cpp
pgadmin sneaks a REINDEX into the SQL when you specify a change to the
fillfactor of an index.
That's not very handy because the Postgres manual says specifically that
ALTER INDEX doesn't issue a REINDEX. It's a perfectly valid thing to run
on its own, since it will affect the future growth of th
It would be great if there was a database-level option so that any new
indexes would default to using CONCURRENTLY.
This would allow production systems to be changed easily using the
default of CONCURRENTLY, whereas dev systems won't need that.
If not, can we just have a general default of use co
Author: dpage
Date: 2007-10-04 14:41:04 +0100 (Thu, 04 Oct 2007)
New Revision: 6710
Revision summary: http://svn.pgadmin.org/cgi-bin/viewcvs.cgi/?rev=6710&view=rev
Log:
Fix the tablespace dialogue to use the new two-part SQL infrastructure as it
seems CREATE TABLESPACE isn't supported in a mul
