Re: tablespaces inside $PGDATA considered harmful

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: tablespaces inside $PGDATA considered harmful
Date: 2015-04-28 21:35:40
Message-ID: 20150428213540.GB31727@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Apr 24, 2015 at 01:05:03PM -0400, Bruce Momjian wrote:
> This way, both pg_dump and pg_upgrade will issue warnings, though, of
> course, those warnings can be ignored. I am hopeful these two warnings
> will be sufficient and we will not need make these errors, with the
> possible inconvenience it will cause. I am still afraid that someone
> will ignore the new errors pg_dump would generate and lose data. I just
> don't remember enough cases where we threw new errors on _data_ restore.
>
> Frankly, those using pg_upgrade already will have to move the old
> tablespaces out of the old cluster if they ever want to delete those
> clusters, so I am hopeful these additional warnings will help eliminate
> this practice, which is already cumbersome and useless. I am not
> planning to revisit this for 9.6.

Patch applied.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ Everyone has their own god. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2015-04-28 21:39:45 Re: FIX : teach expression walker about RestrictInfo
Previous Message Andrew Dunstan 2015-04-28 20:38:54 Re: COPY and file_fdw with fixed column widths