Re: [***DKIM violation***] Re: [PATCH] Fix JSON_SERIALIZE() coercion placeholder type for jsonb input

From: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
To: Staroverov Ilja <i(dot)staroverov(at)ftdata(dot)ru>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, Nikhil Sontakke <nikkhils(at)gmail(dot)com>
Subject: Re: [***DKIM violation***] Re: [PATCH] Fix JSON_SERIALIZE() coercion placeholder type for jsonb input
Date: 2026-10-27 22:02:27
Message-ID: CAN4CZFMzLa4q9y3YDYzkRB6hmj070ragrAToM2GeEY=HoJdLCg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 15 Oct 2026, Staroverov Ilja <i(dot)staroverov(at)ftdata(dot)ru> wrote:
> Given that, I think the fix should be back-patched to 17,

and

On Thu, 27 Aug 2026, NikhilS <nikkhils(at)gmail(dot)com> wrote:
> If no backpatch is intended (which I think is the case here),
> then any concerns about previously stored expression trees does not apply
> for this patch.

Since this can affect both indexes and stored generated columns, I
think the commit message should mention that this can 1. possibly
require a reindex 2. doesn't fix existing stored generated columns
affected by this issue. And the same concern is also true for
backpatching it.

In response to

Browse pgsql-hackers by date

  From Date Subject
Previous Message Haibo Yan 2026-10-27 21:57:31 Re: ICU fixed digit reordering bug