From: | Artem Anisimov <artem(dot)anisimov(dot)255(at)gmail(dot)com> |
---|---|
To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
Cc: | Dmitry Dolgov <9erthalion6(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-14 13:05:51 |
Message-ID: | 70fc3ad6-8c38-d8d7-b690-a1c01f9b1683@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Hi Thomas,
thank you for the fixes. I've looked up the patches in pg's git repo,
and they got me wondering: where is the repo with pg tests? I'd be
really uneasy to make changes to concurrency-related code without a
decent testsuite to verify them.
Best regards,
Artem.
On 04/07/2023 01:02, Thomas Munro wrote:
> 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 | Daniel Gustafsson | 2023-07-14 13:07:08 | Re: pg_basebackup: errors on macOS on directories with ".DS_Store" files |
Previous Message | Andrew Dunstan | 2023-07-14 12:04:18 | Re: pg_dump needs SELECT privileges on irrelevant extension table |