Re: Alvaro Herrera 2014-12-22 <20141222165157.gd1...@alvh.no-ip.org>
> Multi-table CLUSTER uses multiple transactions, so this should not be an
> issue.  That said, I don't think there's much point in CLUSTER SCHEMA,
> much less TRUNCATE SCHEMA.  Do you normally organize your schemas so
> that there are some that contain only tables that need to be truncated
> together?  That would be a strange use case.

Having a schema that's only used for importing data in batch jobs
doesn't sound too unreasonable. It could then be cleaned in a simple
"TRUNCATE SCHEMA import_area" command.

> Overall, this whole line of development seems like bloating the parse
> tables for little gain.

Reading the thread, my impression was that most people opposed the
idea because there's ways to script "vacuum schema", or because of
"people shouldn't be invoking manual vacuums anyway". I think the
patch tries to solve a practical problem, and does have its merits.

Christoph
-- 
c...@df7cb.de | http://www.df7cb.de/


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

Reply via email to