Re: Proposal "VACUUM SCHEMA" - Mailing list pgsql-hackers

From Fabrízio de Royes Mello
Subject Re: Proposal "VACUUM SCHEMA"
Date
Msg-id CAFcNs+r35Hifiv0egdSGz3PWP-yh-XO6ULrGiNgdEBnF04vEjw@mail.gmail.com
Whole thread
In response to Re: Proposal "VACUUM SCHEMA"  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Responses Re: Proposal "VACUUM SCHEMA"
List pgsql-hackers
On Mon, Dec 22, 2014 at 8:02 PM, Jim Nasby <Jim.Nasby@bluetreble.com> wrote:
>
> On 12/21/14, 8:55 PM, Fabrízio de Royes Mello wrote:
>>
>>           > And why that, but not
>>           > say schema-wide ANALYZE, CLUSTER, TRUNCATE, ...
>>           >
>>
>>         +1. I can write patches for each of this maintenance statement too.
>>
>>
>>     If we're going to go that route, then perhaps it would make more sense to create a command that allows you to apply a second command to every object in a schema. We would have to be careful about PreventTransactionChain commands.
>>
>>
>>   Sorry but I don't understand what you meant. Can you explain more about your idea?
>
>
> There's a very large number of commands that could be useful to execute on every object in a schema. (RE)INDEX, CLUSTER, ALTER come to mind besides VACUUM.
>

ANALYZE too...

 

> Right now a lot of people just work around this with things like DO blocks, but as mentioned elsewhere in the thread that fails for commands that can't be in a transaction.
>

I use "dblink" to solve it. :-)


Regards,

--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog: http://fabriziomello.github.io
>> Linkedin: http://br.linkedin.com/in/fabriziomello
>> Twitter: http://twitter.com/fabriziomello
>> Github: http://github.com/fabriziomello

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: pgbench -f and vacuum
Next
From: Adam Brightwell
Date:
Subject: Re: Role Attribute Bitmask Catalog Representation