| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de>, Bruce Momjian <bruce(at)momjian(dot)us>, 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-23 20:17:55 |
| Message-ID: | 55395373.9030006@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 4/23/15 11:01 AM, Andres Freund wrote:
> On April 23, 2015 6:12:05 PM GMT+03:00, Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> wrote:
>> On 4/22/15 9:41 PM, Bruce Momjian wrote:
>>> The case this doesn't catch is referencing a
>>> symbolic link that points to the same directory. We can't make it an
>>> error so people can use pg_upgrade these setups.
>>
>> Couldn't we make it an ERROR unless IsBinaryUpgrade?
>
> People still upgrade without pg upgrade.
Yes, but only after creating a brand new cluster from scratch, which
would then disallow them from putting tablespaces in $PGDATA.
Or are you saying people do binary upgrades without pg_upgrade? I don't
think we have any obligation to support that...
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2015-04-23 20:20:58 | Re: tablespaces inside $PGDATA considered harmful |
| Previous Message | Andres Freund | 2015-04-23 20:14:28 | Re: INSERT ... ON CONFLICT IGNORE (and UPDATE) 3.0 |