Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part

From: "David E(dot) Wheeler" <david(at)justatheory(dot)com>
To: Florents Tselai <florents(dot)tselai(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Alexander Korotkov <aekorotkov(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>
Subject: Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part
Date: 2025-07-10 18:13:13
Message-ID: 84727E10-62B7-4FE4-B487-E7044C7C0A1F@justatheory.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Jul 10, 2025, at 13:41, Florents Tselai <florents(dot)tselai(at)gmail(dot)com> wrote:

> The basic problem I see with these latest revisions/refactorings is that they fail for pg_upgrade afaict.
> Probably this means that some of the rearrangements on the parser/scanner are not that flexible.

Oh, is that what’s happening? What needs to happen to properly support pg_upgrade?

Best,

David

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-07-10 18:16:04 Re: Why our Valgrind reports suck
Previous Message Andrew Dunstan 2025-07-10 18:08:01 Re: C11 / VS 2019