From: | Michel Pelletier <pelletier(dot)michel(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Using Expanded Objects other than Arrays from plpgsql |
Date: | 2024-11-02 00:53:14 |
Message-ID: | CACxu=vL7i_U_iSNpREe8eCAMEyKHuPpk9THRpBhk+ar0U1EdOw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On Fri, Nov 1, 2024 at 3:27 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Michel Pelletier <pelletier(dot)michel(at)gmail(dot)com> writes:
>
> Here is a v1 patch series that does the first part of what we've been
> talking about, which is to implement the new optimization rule for
> the case of a single RHS reference to the target variable. I'm
> curious to know if it helps you at all by itself. You'll definitely
> also need commit 534d0ea6c, so probably applying these on our git
> master branch would be the place to start.
>
I'll apply these tonight and get back to you asap. There are many
functions in my API that take only one expanded RHS argument, so I'll look
for some cases where your changes reduce expansions when I run my tests.
Thank you!
-Michel
From | Date | Subject | |
---|---|---|---|
Next Message | Thiemo Kellner | 2024-11-02 07:13:34 | Re: Plans for partitioning of inheriting tables |
Previous Message | Michel Pelletier | 2024-11-02 00:50:52 | Re: Using Expanded Objects other than Arrays from plpgsql |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2024-11-02 01:28:06 | Re: Doc: typo in config.sgml |
Previous Message | Michel Pelletier | 2024-11-02 00:50:52 | Re: Using Expanded Objects other than Arrays from plpgsql |