| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Alexander Pyhalov <a(dot)pyhalov(at)postgrespro(dot)ru> |
| Subject: | Re: Performance issues with v18 SQL-language-function changes |
| Date: | 2025-04-16 17:50:44 |
| Message-ID: | CAFj8pRDNm-BcJuqYe=A0FAVj3VaBAKSGBgKmX7Gjhjy94ZZ7Ng@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi
st 16. 4. 2025 v 19:43 odesílatel Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> napsal:
> Bruce Momjian <bruce(at)momjian(dot)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.
>
yes, and for most cases it has significant performance benefits. For a few
corner cases, there can be some slowdown that can be fixed by last Tom
patches.
Regards
Pavel
> regards, tom lane
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Lakhin | 2025-04-16 18:00:00 | Re: recoveryCheck test failure on flaviventris |
| Previous Message | Álvaro Herrera | 2025-04-16 17:44:21 | Re: pgsql: Non text modes for pg_dumpall, correspondingly change pg_restore |