Re: Fix missing FORMAT when deparsing JSON_ARRAY(query)

From: Richard Guo <guofenglinux(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, John Naylor <johncnaylorls(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Fix missing FORMAT when deparsing JSON_ARRAY(query)
Date: 2026-07-28 05:41:11
Message-ID: CAMbWs48dzgnP5mEbAga8ZNJoBbZ0hnRbqP+okLR33=BfEqN0gA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jul 27, 2026 at 10:43 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Pushed. BTW, while I was doing that I noticed that your predecessor
> commits (f4c850d11, aa50f4f02) assigned the same catversion 202607271
> in both branches. That's not good practice: it's likely that there
> are already other discrepancies between v19 and v20 catalogs, and
> in any case the whole point of the catversion mechanism is to prevent
> confusion. You can use the same date in both branches, but use
> different last digits. In my change, I used 202607272 for v19 and
> 202607273 for master.

That's good to know! Thanks for making the change.

- Richard

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message shveta malik 2026-07-28 05:41:16 Re: A new C function `get_partition_root`.
Previous Message Jacob Brazeal 2026-07-28 05:36:30 serializable anomaly - duplicate primary keys