Re: pg_dump to support "on conflict do update"

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

That's reasonable. Thank you.

On Sat, May 3, 2025 at 12:31 PM David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:

> 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

Browse pgsql-hackers by date

  From Date Subject
Next Message Álvaro Herrera 2025-05-03 20:46:59 Re: pg_dump to support "on conflict do update"
Previous Message Jelte Fennema-Nio 2025-05-03 19:40:47 Re: PG 18 release notes draft committed