Re: Performance issues with v18 SQL-language-function changes - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Performance issues with v18 SQL-language-function changes
Date
Msg-id 2031695.1744825426@sss.pgh.pa.us
Whole thread Raw
In response to Re: Performance issues with v18 SQL-language-function changes  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Performance issues with v18 SQL-language-function changes
Re: Performance issues with v18 SQL-language-function changes
List pgsql-hackers
Bruce Momjian <bruce@momjian.us> writes:
> On Mon, Apr 14, 2025 at 10:38:29AM -0400, Robert Haas wrote:
>> I agree that we should do something about this. I haven't reviewed
>> your patches but the approach sounds broadly reasonable.

> Yep, we went down the road in PG 18 to convert syntax, and now we have
> to fix this, or we have to revert all the PG 18 syntax changes, which
> seems like a step backward.

I'm confused?  0dca5d68d didn't have anything to do with
syntax changes, just with when planning happens.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_dump --if-exists --clean when drop index that is partition of a partitioned index
Next
From: Álvaro Herrera
Date:
Subject: Re: pgsql: Non text modes for pg_dumpall, correspondingly change pg_restore