Re: Tablespaces - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Tablespaces
Date
Msg-id 20085.1077900166@sss.pgh.pa.us
Whole thread Raw
In response to Re: Tablespaces  ("scott.marlowe" <scott.marlowe@ihs.com>)
List pgsql-hackers
"scott.marlowe" <scott.marlowe@ihs.com> writes:
> On Fri, 27 Feb 2004, Zeugswetter Andreas SB SD wrote:
>>> How would it get to be empty?  Are you thinking of some sort of "connect
>>> database to tablespace" and "disconnect database from tablespace"
>>> commands that would respectively create and delete the per-database
>>> subdirectory?  That seems moderately reasonable to me.  We could then
>> 
>> I would only allow the drop if the directory only contains empty db oid 
>> directories.

That's subject to race conditions (ie, someone creating a table about
the same time you are deciding it's okay to drop the tablespace).  There
needs to be some interlock, and I think that associating that lock with
infrequently executed connect/disconnect operations would be good from a
performance standpoint.

> Wouldn't this be better tracked in the dependency tracking that's already 
> built into postgresql?

No, because dependencies are local to individual databases.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: CVS HEAD compile warning
Next
From: Lee Kindness
Date:
Subject: Re: Thread safe connection-name mapping in ECPG. Is it