Laurenz Albe writes:
> On Sat, 2025-05-03 at 22:47 -0700, Tanin Na Nakorn wrote:
>> Here's the patch (against the latest master) that will make pg_dump support
>> "on conflict do update" .
>>
>> There are 3 caveats:
>>
>> 1. The "on conflict do update" would apply to every table. In my opinion,
On Sat, 2025-05-03 at 22:47 -0700, Tanin Na Nakorn wrote:
> Here's the patch (against the latest master) that will make pg_dump support
> "on conflict do update" .
>
> I've used this patch on v16 for our company's CI (on Github Actions), and it
> works perfectly fine.
>
> Users would be able to
Hi hackers,
Here's the patch (against the latest master) that will make pg_dump support
"on conflict do update" .
I've used this patch on v16 for our company's CI (on Github Actions), and
it works perfectly fine.
Users would be able to use it like this:
./src/bin/pg_dump/pg_dump $DATABASE_URL \
