Postgres Pro
Downloads
Home   >   mailing lists

Re: BUG #17949: Adding an index introduces serialisation anomalies. - Mailing list pgsql-bugs

From Thomas Munro
Subject Re: BUG #17949: Adding an index introduces serialisation anomalies.
Date
Msg-id CA+hUKGKRD5UM6mEDkre-yhm9Smr4ampf-5=NeFkAqi-jRt4RYQ@mail.gmail.com
Whole thread Raw
In response to Re: BUG #17949: Adding an index introduces serialisation anomalies.  (Thomas Munro <thomas.munro@gmail.com>)
Responses Re: BUG #17949: Adding an index introduces serialisation anomalies.  (Dmitry Dolgov <9erthalion6@gmail.com>)
List pgsql-bugs
Tree view 
On Wed, Jun 21, 2023 at 10:54 AM Thomas Munro <thomas.munro@gmail.com> wrote:
> This is probably going to go faster if I CC the authors of commit
> 0bef1c06.  Any ideas about how we're missing rw-conflicts under high
> concurrency?

I guess one (probably stupid) question I have: where is the
CheckForSerializableConflictIn(rootPostingTree) that I was expecting
to see when writing to an existing posting tree?  IIUC that should
pair with PredicateLockPage(btree->index, rootPostingTree, snapshot)
when reading.

pgsql-bugs by date:

Previous
From: David Rowley
Date:
Subject: Re: BUG #17975: Nested Loop Index Scan returning wrong result
Next
From: Tomas Vondra
Date:
Subject: Re: BUG #17986: Inconsistent results of SELECT affected by btree index