Re: BUG #17949: Adding an index introduces serialisation anomalies.

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Dmitry Dolgov <9erthalion6(at)gmail(dot)com>
Cc: artem(dot)anisimov(dot)255(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org, Teodor Sigaev <teodor(at)sigaev(dot)ru>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Subject: Re: BUG #17949: Adding an index introduces serialisation anomalies.
Date: 2023-06-20 23:20:28
Message-ID: CA+hUKGKRD5UM6mEDkre-yhm9Smr4ampf-5=NeFkAqi-jRt4RYQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Jun 21, 2023 at 10:54 AM Thomas Munro <thomas(dot)munro(at)gmail(dot)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.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tomas Vondra 2023-06-20 23:40:56 Re: BUG #17986: Inconsistent results of SELECT affected by btree index
Previous Message David Rowley 2023-06-20 23:01:39 Re: BUG #17975: Nested Loop Index Scan returning wrong result