Re: pg_dump to support "on conflict do update"

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Tanin Na Nakorn <tanin(at)klutchlabs(dot)ai>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: pg_dump to support "on conflict do update"
Date: 2025-05-03 19:30:52
Message-ID: CAKFQuwa0Ty8UOiX4Wy=OTt_bxSjAOUWxz5vQJ1NqjtFbfpqsfQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, May 3, 2025 at 12:08 PM Tanin Na Nakorn <tanin(at)klutchlabs(dot)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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jelte Fennema-Nio 2025-05-03 19:40:47 Re: PG 18 release notes draft committed
Previous Message Andrei Lepikhov 2025-05-03 18:44:43 Re: making EXPLAIN extensible