Stephen Frost <sfr...@snowman.net> writes: > Yes. I'd definitely like to see an ALTER TABLESPACE option, with an > ERROR that lists out all of the non-temporary objects which are found > (and lists any other databases which have objects in those > tablespaces..). That would allow administrators who have existing > notionally temporary-only tablespaces to go clean things up to make them > actually temporary-only.
That seems just about impossible from a concurrency standpoint (ie, what if someone is creating a new table in the tablespace concurrently with your check? Possibly in a different database?) I would certainly suggest that the first version of the patch not undertake to allow this property to be ALTERed; the cost-benefit ratio isn't there IMO. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers