Joost Kraaijeveld wrote:
Hi,
I am using auto-vacuum (autovacuum = on) but sometimes PGAdmin warns me
that I need to enable autovacuum or do it manually.
How does PgAdmin determine that it is necessary to run vacuum?
Using the following code:
bool pgTable::GetVacuumHint()
{
bool canHint=f
Milen A. Radev wrote:
I consider the decision to distinguish between functions and procedures
in pgAdmin's UI very unfortunate.
It's a historic thing - procedures actually appeared in early versions
of EnterpriseDB originally where they were considered different objects
from functions if mem
Andrus wrote:
pgAdmin already has a "Drop Cascaded" option that works for schemas.
Just right-click the object to drop.
Dave,
thank you. It works.
I expected that Del command runs drop cascaded .
It would be better to make drop always cascaded.
This would allow to remove drop cascaded menu i
Hi,
I am using auto-vacuum (autovacuum = on) but sometimes PGAdmin warns me
that I need to enable autovacuum or do it manually.
How does PgAdmin determine that it is necessary to run vacuum?
TIA
--
Groeten,
Joost Kraaijeveld
Askesis B.V.
Molukkenstraat 14
6524NB Nijmegen
tel: 024-3888063 / 06
To reproduce:
create table foo ( bar char(20));
CREATE UNIQUE INDEX bar_pattern_idx ON foo(LOWER(bar) text_pattern_ops);
Observed in pgAdmin 1.6 post beta-1 table definition pane:
CREATE UNIQUE INDEX bar_pattern_idx
ON foo
USING btree
(lower(bar::text));
Expected:
text_pattern_ops must b