答复: BUG #15207: In crash recovery, SyncDataDirectory() will fall into recursion trap - Mailing list pgsql-bugs

From shao bret
Subject 答复: BUG #15207: In crash recovery, SyncDataDirectory() will fall into recursion trap
Date
Msg-id KL1PR0201MB21175D955D3A940CEA1DE4F6E66A0@KL1PR0201MB2117.apcprd02.prod.outlook.com
Whole thread Raw
In response to Re: BUG #15207: In crash recovery, SyncDataDirectory() will fallinto recursion trap  (Michael Paquier <michael@paquier.xyz>)
List pgsql-bugs

 

I have got the history of this issue.

 

Thanks.

 

Br.

Bret

发送自 Windows 10 邮件应用

 

发件人: Michael Paquier
发送时间: 2018523 22:03
收件人: Tom Lane
抄送: bret.shao@outlook.com; pgsql-bugs@lists.postgresql.org
主题: Re: BUG #15207: In crash recovery, SyncDataDirectory() will fall into recursion trap

 

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

 

pgsql-bugs by date:

Previous
From: Jeremy Schneider
Date:
Subject: Re: BUG #14820: Standby crash with "could not access status oftransaction" (for track_commit_timestamp)
Next
From: "Anjul Tyagi"
Date:
Subject: PGADMIN4 V3.0 Error