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 \
That's reasonable. Thank you.
On Sat, May 3, 2025 at 12:31 PM David G. Johnston <
david.g.johns...@gmail.com> wrote:
> On Sat, May 3, 2025 at 12:08 PM Tanin Na Nakorn
> wrote:
>
>> 3. Is it possible to patch this into the version 16 as well as the
>> version 17 a
Hi hackers,
I've made a proof of concept for pg_dump to support "on conflict do update"
here: https://github.com/tanin47/postgres/pull/1
It can be used with the following options: --on-conflict-target-columns
url,payload_checksum
--on-conflict-update-clause='last_used_at=EXCLUDED.last_used_at'
I
