<div dir="ltr"><div class="gmail_extra">On Mon, Dec 22, 2014 at 8:02 PM, Jim Nasby <<a
href="mailto:Jim.Nasby@bluetreble.com">Jim.Nasby@bluetreble.com</a>>wrote:<br />><br />> On 12/21/14, 8:55 PM,
Fabríziode Royes Mello wrote:<br />>><br />>> > And why that, but not<br />>>
>say schema-wide ANALYZE, CLUSTER, TRUNCATE, ...<br />>> ><br />>><br />>>
+1.I can write patches for each of this maintenance statement too.<br />>><br />>><br />>> If
we'regoing to go that route, then perhaps it would make more sense to create a command that allows you to apply a
secondcommand to every object in a schema. We would have to be careful about PreventTransactionChain commands.<br
/>>><br/>>><br />>> Sorry but I don't understand what you meant. Can you explain more about your
idea?<br/>><br />><br />> There's a very large number of commands that could be useful to execute on every
objectin a schema. (RE)INDEX, CLUSTER, ALTER come to mind besides VACUUM.<br />><br /><br />ANALYZE too...<br /><br
/> <br/><br />> Right now a lot of people just work around this with things like DO blocks, but as mentioned
elsewherein the thread that fails for commands that can't be in a transaction.<br />><br /><br />I use "dblink" to
solveit. :-)<br /><br /><br /></div><div class="gmail_extra">Regards,<br /><br /></div><div class="gmail_extra">--<br
/>Fabríziode Royes Mello<br />Consultoria/Coaching PostgreSQL<br />>> Timbira: <a
href="http://www.timbira.com.br">http://www.timbira.com.br</a><br/>>> Blog: <a
href="http://fabriziomello.github.io">http://fabriziomello.github.io</a><br/>>> Linkedin: <a
href="http://br.linkedin.com/in/fabriziomello">http://br.linkedin.com/in/fabriziomello</a><br/>>> Twitter: <a
href="http://twitter.com/fabriziomello">http://twitter.com/fabriziomello</a><br/>>> Github: <a
href="http://github.com/fabriziomello">http://github.com/fabriziomello</a></div></div>
