| From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
|---|---|
| To: | Zeugswetter Andreas SB SD <ZeugswetterA(at)spardat(dot)at> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Gavin Sherry <swm(at)linuxworld(dot)com(dot)au>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Tablespaces |
| Date: | 2004-02-27 15:27:02 |
| Message-ID: | Pine.LNX.4.33.0402270826070.13785-100000@css120.ihs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Brusser | 2004-02-27 15:27:20 | Re: Question on pg_dump |
| Previous Message | Michael Meskes | 2004-02-27 15:24:31 | Re: Thread safe connection-name mapping in ECPG. Is it |