From: | Dmitry Dolgov <9erthalion6(at)gmail(dot)com> |
---|---|
To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
Cc: | artem(dot)anisimov(dot)255(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #17949: Adding an index introduces serialisation anomalies. |
Date: | 2023-06-21 08:58:12 |
Message-ID: | 20230621085812.idputjd7w3ejjih3@ddolgov.remote.csb |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
> On Tue, Jun 20, 2023 at 01:22:19PM +1200, Thomas Munro wrote:
> On Tue, Jun 20, 2023 at 12:18 AM Dmitry Dolgov <9erthalion6(at)gmail(dot)com> wrote:
> > > On Mon, Jun 19, 2023 at 09:30:12PM +1200, Thomas Munro wrote:
> > > +#if 0
> > > /*
> > > * Ignore any claimed entries past what we think is the end of the
> > > * relation. It may have been extended after the start of our scan (we
> > > * only hold an AccessShareLock, and it could be inserts from this
> > > * backend).
> > > */
> > > if (block >= hscan->rs_nblocks)
> > > return false;
> > > +#endif
> >
> > Great, thanks! Can confirm, after applying both the posted patch and the
> > change above the issue is not reproducible anymore.
>
> Here's a cleaned-up version of the first two changes. What do you
> think about the assertions I make in the commit message for 0002?
Yep, it sounds correct to me. After a quick look I couldn't find where
exactly the similar code lives in the pre-tableam version, so can't say
anything about back-patching there.
From | Date | Subject | |
---|---|---|---|
Next Message | Dmitry Dolgov | 2023-06-21 09:04:21 | Re: BUG #17949: Adding an index introduces serialisation anomalies. |
Previous Message | Zu-Ming Jiang | 2023-06-21 07:22:38 | Re: BUG #17986: Inconsistent results of SELECT affected by btree index |