From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Grzegorz Jaskiewicz <gj(at)pointblue(dot)com(dot)pl> |
Cc: | PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Hot standby, dropping a tablespace |
Date: | 2009-01-26 09:09:49 |
Message-ID: | 1232960989.2327.1473.camel@ebony.2ndQuadrant |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, 2009-01-25 at 12:13 +0000, Grzegorz Jaskiewicz wrote:
> On 2009-01-25, at 09:04, Simon Riggs wrote:
>
> >
> > On Sat, 2009-01-24 at 21:58 +0200, Heikki Linnakangas wrote:
> >> When replaying a DROP TABLE SPACE, you first try to remove the
> >> directory, and if that fails, you assume that it's because it's in
> >> use
> >> as a temp tablespace in a read-only transaction.
> >
> > That sounds like you think there another conclusion?
>
> What if subdirectory of that directory is owned by root ?
> Say I create /home/gj/tablespace1 . Surely emptying it is possible,
> but should it remove the dir altogether ?
> It is possible to create tablespace in that directory, even so
> postgres user doesn't own /home/gj/ directory. So why shouldn't it be
> possible to drop it ?
This is not a question for the Hot Standby patch to answer. Recovery is
just trying to emulate what happens in normal running, nothing more.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2009-01-26 10:18:13 | Re: Hot standby, dropping a tablespace |
Previous Message | Simon Riggs | 2009-01-26 09:00:14 | Re: Hot standby, dropping a tablespace |