<div dir="ltr"><div class="gmail_extra">On Wed, Jun 18, 2014 at 1:59 PM, Tom Lane <<a
href="mailto:tgl@sss.pgh.pa.us">tgl@sss.pgh.pa.us</a>>wrote:<br />><br />> Stephen Frost <<a
href="mailto:sfrost@snowman.net">sfrost@snowman.net</a>>writes:<br /> > > Yes. I'd definitely like to see an
ALTERTABLESPACE option, with an<br />> > ERROR that lists out all of the non-temporary objects which are found<br
/>>> (and lists any other databases which have objects in those<br /> > > tablespaces..). That would allow
administratorswho have existing<br />> > notionally temporary-only tablespaces to go clean things up to make
them<br/>> > actually temporary-only.<br />><br />> That seems just about impossible from a concurrency
standpoint<br/> > (ie, what if someone is creating a new table in the tablespace<br />> concurrently with your
check? Possibly in a different database?)<br />><br /><br /></div><div class="gmail_extra">You are correct, I
completelyforgot that CREATE TABLESPACE is not transaction safe.<br /></div><div class="gmail_extra"><br /><br />> I
wouldcertainly suggest that the first version of the patch not<br />> undertake to allow this property to be
ALTERed;the cost-benefit<br />> ratio isn't there IMO.<br /> ><br /><br />+1<br /><br /></div><div
class="gmail_extra">Regards,<br/></div><div class="gmail_extra"><br />--<br />Fabrízio de Royes Mello<br
/>Consultoria/CoachingPostgreSQL<br />>> Timbira: <a
href="http://www.timbira.com.br">http://www.timbira.com.br</a><br/> >> Blog sobre TI: <a
href="http://fabriziomello.blogspot.com">http://fabriziomello.blogspot.com</a><br/>>> Perfil 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></div></div>
