From: | shao bret <bret(dot)shao(at)outlook(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | 答复: BUG #15207: In crash recovery, SyncDataDirectory() will fall into recursion trap |
Date: | 2018-05-24 01:41:32 |
Message-ID: | KL1PR0201MB21175D955D3A940CEA1DE4F6E66A0@KL1PR0201MB2117.apcprd02.prod.outlook.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
I have got the history of this issue.
Thanks.
Br.
Bret
发送自 Windows 10 版邮件<https://go.microsoft.com/fwlink/?LinkId=550986>应用
发件人: Michael Paquier<mailto:michael(at)paquier(dot)xyz>
发送时间: 2018年5月23日 22:03
收件人: Tom Lane<mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us>
抄送: bret(dot)shao(at)outlook(dot)com<mailto:bret(dot)shao(at)outlook(dot)com>; pgsql-bugs(at)lists(dot)postgresql(dot)org<mailto:pgsql-bugs(at)lists(dot)postgresql(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Anjul Tyagi | 2018-05-24 07:56:54 | PGADMIN4 V3.0 Error |
Previous Message | Jeremy Schneider | 2018-05-23 21:20:23 | Re: BUG #14820: Standby crash with "could not access status of transaction" (for track_commit_timestamp) |