Re: INSERT ... ON CONFLICT DO SELECT [FOR ...] take 2 - Mailing list pgsql-hackers

From v@viktorh.net
Subject Re: INSERT ... ON CONFLICT DO SELECT [FOR ...] take 2
Date
Msg-id 91BEF220-A4D2-423E-96CF-384813432C3C@viktorh.net
Whole thread Raw
In response to Re: INSERT ... ON CONFLICT DO SELECT [FOR ...] take 2  (Dean Rasheed <dean.a.rasheed@gmail.com>)
List pgsql-hackers
Hello, I was working on my own patch for the same thing, until I found this was already there.
I think this would be very useful for a lot of people.
Do you need any help moving this forward Anderas? I have both tests and docs written, although not for the FOR UPDATE
part.

> On 25 Jun 2025, at 13:39, Dean Rasheed <dean.a.rasheed@gmail.com> wrote:
>
> On Mon, 12 May 2025 at 19:33, Andreas Karlsson <andreas@proxel.se> wrote:
>>
>> I have fixed that one and some other issues locally and will submit a
>> new version in a while after I have added more tests because you are
>> very correct in that a big issue with my last version of the patch was
>> the big lack of tests and lack of making sure all features which
>> interact with UPSERT actually worked with my changes. Plus some islation
>> tests would be nice to have.
>>
>
> +1. Don't forget to move the CF entry to the next open CF.
>
> FYI, over on [1] I proposed more tests and doc updates for RLS. I
> think those updates might make it easier to test and document the RLS
> aspects of this patch.
>
> [1] https://www.postgresql.org/message-id/flat/CAEZATCWqnfeChjK=n1V_dYZT4rt4mnq+ybf9c0qXDYTVMsy8pg@mail.gmail.com
>
> Regards,
> Dean
>
>
>




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Disabling memory overcommit deemed dangerous
Next
From: Ranier Vilela
Date:
Subject: Get ride of pqbool artifact (src/interfaces/libpq/libpq-fe.h)