From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
---|---|
To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
Cc: | Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, artem(dot)anisimov(dot)255(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org, Teodor Sigaev <teodor(at)sigaev(dot)ru> |
Subject: | Re: BUG #17949: Adding an index introduces serialisation anomalies. |
Date: | 2023-07-03 22:02:03 |
Message-ID: | CA+hUKG+DkBG4gBy_5+vj31ySHJB4XWgaaA4y=coosGf2Qz81yQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Wed, Jun 28, 2023 at 3:18 PM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> I'll push these in a couple of days if there are no further comments.
Done.
Thanks Artem, Dmitry and Heikki.
I wonder how we might be more systematic about this. There are some
general principles that were not respected here, but I'm not sure if
they're even written down let alone defended with code. Something to
think about.
It's not great to add a new use of BufferGetBlockNumber() (in terms of
false sharing just to get a value that we must have had moment earlier
in order to pin the buffer), but we do that all the time. That seems
like a micro-optimisation worth looking into in some systematic way
across all AMs.
From | Date | Subject | |
---|---|---|---|
Next Message | shveta malik | 2023-07-04 03:26:53 | Re: Backend handling replication slot stuck using 100% cpu, unkillable |
Previous Message | Joe Conway | 2023-07-03 16:31:09 | Re: BUG #17946: LC_MONETARY & DO LANGUAGE plperl - BUG |