Re: BUG #15207: In crash recovery, SyncDataDirectory() will fall into recursion trap

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: bret(dot)shao(at)outlook(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15207: In crash recovery, SyncDataDirectory() will fall into recursion trap
Date: 2018-05-23 14:02:52
Message-ID: 20180523140252.GA1934@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, May 23, 2018 at 09:36:33AM -0400, Tom Lane wrote:
> Offhand, I think we do not support tablespaces that are physically inside
> the data directory, either.

pg_upgrade and pg_basebackup work funnily in such cases.

> I think there's been some discussion of having CREATE TABLESPACE try to
> detect and reject such cases. But it would be easy enough to fool it
> (through symlinks, variant path spellings, etc), that people haven't been
> excited about adding such a check.

33cb8ff6 has added a warning when doing this operation. Here is the
related thread:
https://www.postgresql.org/message-id/CA%2BTgmobZLyLU8tFCbMqbjMWB6t%2B%3DERaDo820uQEJCVAQK_Paow%40mail.gmail.com
--
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message SQLpro 2018-05-23 20:12:27 Primary key error in INFORMATION_SCHEMA views
Previous Message Tom Lane 2018-05-23 13:36:33 Re: BUG #15207: In crash recovery, SyncDataDirectory() will fall into recursion trap