From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | José Luis Tallón <jltallon(at)adv-solutions(dot)net>, Fabrízio Mello <fabriziomello(at)gmail(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Proposal "VACUUM SCHEMA" |
Date: | 2014-12-23 15:28:35 |
Message-ID: | 20141223152835.GN1768@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas wrote:
> On Mon, Dec 22, 2014 at 11:51 AM, Alvaro Herrera
> <alvherre(at)2ndquadrant(dot)com> wrote:
> > 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.
> >
> > Overall, this whole line of development seems like bloating the parse
> > tables for little gain.
>
> We added REINDEX SCHEMA less than three weeks ago; if we accept that
> that was a good change, but think this is a bad one, it's not clear to
> me that there is any guiding principle here beyond who happened to
> weigh in on which threads.
I didn't think much of REINDEX SCHEMA, TBH.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2014-12-23 15:34:47 | Re: [COMMITTERS] pgsql: Use a bitmask to represent role attributes |
Previous Message | Alvaro Herrera | 2014-12-23 15:26:30 | Re: [COMMITTERS] pgsql: Use a bitmask to represent role attributes |