Re: Possible corruption by CreateRestartPoint at promotion

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: michael(at)paquier(dot)xyz, 875941708(at)qq(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Possible corruption by CreateRestartPoint at promotion
Date: 2022-04-28 02:50:26
Message-ID: 20220428.115026.562363194579042541.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At Wed, 27 Apr 2022 01:31:55 -0400, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote in
> Michael Paquier <michael(at)paquier(dot)xyz> writes:
> > On Wed, Apr 27, 2022 at 12:36:10PM +0800, Rui Zhao wrote:
> >> Do you have interest in adding a test like one in my patch?
>
> > I have studied the test case you are proposing, and I am afraid that
> > it is too expensive as designed.
>
> That was my feeling too. It's certainly a useful test for verifying
> that we fixed the problem, but that doesn't mean that it's worth the
> cycles to add it as a permanent fixture in check-world, even if we
> could get rid of the timing assumptions.

My first feeling is the same. And I don't find a way to cause this
cheap and reliably without inserting a dedicate debugging-aid code.

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2022-04-28 03:11:37 Re: pgsql: Add contrib/pg_walinspect.
Previous Message Kyotaro Horiguchi 2022-04-28 02:43:57 Re: Possible corruption by CreateRestartPoint at promotion