On 12/22/14, 10:05 AM, Andres Freund wrote:
While the feature itself might be fairly innocuous, I'm just wondering
>why we need to encourage manual vacuuming.  And why that, but not
>say schema-wide ANALYZE, CLUSTER, TRUNCATE, ...
There's one argument for supporting more for VACUUM than the rest - it
can't be executed directly as the result of a query as the others
can... I wonder if that'd not better be answered by adding a feature to
vacuumdb that allows selecting the to-be-vacuumed table by a user
defined query.

I would MUCH rather that we find a way to special-case executing 
non-transactional commands dynamically, because VACUUM isn't the only one that 
suffers from this problem.
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com

Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:

Reply via email to