From: | "Jaime Casanova" <jcasanov(at)systemguards(dot)com(dot)ec> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: avoid create a tablespace in pg_tblspc |
Date: | 2008-10-09 23:27:24 |
Message-ID: | 3073cc9b0810091627o1dc8ee05ofeed6de6d7373862@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Oct 9, 2008 at 6:22 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Jaime Casanova" <jcasanov(at)systemguards(dot)com(dot)ec> writes:
>> bug report http://archives.postgresql.org/pgsql-bugs/2008-10/msg00037.php
>> seems like a reasonably request to me... and one that is simple to
>> fulfill, just create a PG_VERSION in the pg_tblspc dir at initdb.
>
> I don't think it's a reasonable request. If we take this seriously,
> we'd have to buy into making sure that no subdirectory of $PGDATA is
> ever empty. Which is silly. And what of empty directories elsewhere?
> There are any number of ways to shoot yourself in the foot with a bad
> choice of tablespace location --- I don't find this one more dangerous
> than any other.
>
well, this one can at least create a tablespace that never can be dropped
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
From | Date | Subject | |
---|---|---|---|
Next Message | Emmanuel Cecchet | 2008-10-09 23:30:17 | Re: Transactions and temp tables |
Previous Message | Tom Lane | 2008-10-09 23:22:52 | Re: avoid create a tablespace in pg_tblspc |