From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: tablespaces inside $PGDATA considered harmful |
Date: | 2015-04-24 11:16:47 |
Message-ID: | CA+TgmobzkskAhPt7fG7uYe=sfknMRgnfU7ZgYsXcVOA8vbPhUQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Apr 23, 2015 at 4:30 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> On 2015-04-23 16:26:09 -0400, Robert Haas wrote:
>> But pg_upgrade automates all that, so you can't use pg_upgrade in that
>> case. If we add a GUC as I suggested, you can still use pg_upgrade.
>
> But we also have to live with data directories being in a shit state
> forever onward. We won't really be able to remove the option
> realistically.
>
> It's not that hard to just move the tablespace out of the data directory
> while the server. As long as you move it on the same partition, it's
> even fast.
OK, fair point.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2015-04-24 11:22:28 | Re: PL/pgSQL, RAISE and error context |
Previous Message | Robert Haas | 2015-04-24 11:16:18 | Re: PL/pgSQL, RAISE and error context |