Re: Tablespaces - Mailing list pgsql-hackers

From scott.marlowe
Subject Re: Tablespaces
Date
Msg-id Pine.LNX.4.33.0402270826070.13785-100000@css120.ihs.com
Whole thread Raw
In response to Re: Tablespaces  ("Zeugswetter Andreas SB SD" <ZeugswetterA@spardat.at>)
Responses Re: Tablespaces  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, 27 Feb 2004, Zeugswetter Andreas SB SD wrote:

> 
> > > Ahh. I forgot to detail my ideas on this. It seems to me that we cannot
> > > drop a table space until the directory is empty.
> 
> Agreed.
> 
> > 
> > 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.

Wouldn't this be better tracked in the dependency tracking that's already 
built into postgresql?  Checking to see if the directory is empty is open 
to race conditions, but locking the dependency tracking while dropping a 
tablespace isn't.




pgsql-hackers by date:

Previous
From: Shridhar Daithankar
Date:
Subject: Re: Thread safe connection-name mapping in ECPG. Is it
Next
From: "scott.marlowe"
Date:
Subject: Re: Tablespaces