Re: pg_dump to support "on conflict do update" - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: pg_dump to support "on conflict do update"
Date
Msg-id CAKFQuwa0Ty8UOiX4Wy=OTt_bxSjAOUWxz5vQJ1NqjtFbfpqsfQ@mail.gmail.com
Whole thread Raw
In response to pg_dump to support "on conflict do update"  (Tanin Na Nakorn <tanin@klutchlabs.ai>)
Responses Re: pg_dump to support "on conflict do update"
List pgsql-hackers
On Sat, May 3, 2025 at 12:08 PM Tanin Na Nakorn <tanin@klutchlabs.ai> wrote:
3. Is it possible to patch this into the version 16 as well as the version 17 and latest main branch? Because I use v16.


New features are never back-ported into prior versions.  Feature freeze for v18 just happened meaning any new features will end up in v19 at the earliest.

David J.

pgsql-hackers by date:

Previous
From: Andrei Lepikhov
Date:
Subject: Re: making EXPLAIN extensible
Next
From: Jelte Fennema-Nio
Date:
Subject: Re: PG 18 release notes draft committed