| From: | Grzegorz Jaskiewicz <gj(at)pointblue(dot)com(dot)pl> |
|---|---|
| To: | PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Hot standby, dropping a tablespace |
| Date: | 2009-01-25 12:13:44 |
| Message-ID: | 72CC9A49-CC73-47E0-908B-845E3A454AD0@pointblue.com.pl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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 ?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2009-01-25 12:15:17 | Re: V4 of PITR performance improvement for 8.4 |
| Previous Message | Bernd Helmle | 2009-01-25 12:07:09 | Re: [COMMITTERS] pgsql: Automatic view update rules Bernd Helmle |