MIME-Version: 1.0
References: <CACxu=vJaKFNsYxooSnW1wEgsAO5u_v1XYBacfVJ14wgJV_PYeg@mail.gmail.com>
 <1342498.1729444411@sss.pgh.pa.us> <CACxu=vLXvpzN4X3k+9jsMt6ujuOvFVUSkA80t_cROSsF4y2jQQ@mail.gmail.com>
 <1445998.1729482404@sss.pgh.pa.us> <CACxu=vKEF8Qa-OaADFxf0uMg-xw6gH_CNCWd2s+xaqh-gY4=xg@mail.gmail.com>
 <2062830.1729625620@sss.pgh.pa.us> <2265411.1729699470@sss.pgh.pa.us>
 <CACxu=v++HNmss59yGUDkRny7g=M8tZ2YXF07AUXqKVGqcSfxGQ@mail.gmail.com>
 <2354718.1729737539@sss.pgh.pa.us> <2581216.1729794746@sss.pgh.pa.us>
 <CACxu=v+dn37zr8gx5xNP-EZY3OLtGLTHrbx_ZkCQc40HpyMLKA@mail.gmail.com> <1948345.1730500073@sss.pgh.pa.us>
In-Reply-To: <1948345.1730500073@sss.pgh.pa.us>
From: Michel Pelletier <pelletier.michel@gmail.com>
Date: Fri, 1 Nov 2024 17:53:14 -0700
Message-ID: <CACxu=vL7i_U_iSNpREe8eCAMEyKHuPpk9THRpBhk+ar0U1EdOw@mail.gmail.com>
Subject: Re: Using Expanded Objects other than Arrays from plpgsql
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@lists.postgresql.org
Content-Type: multipart/alternative; boundary="0000000000001b8c700625e37ca0"
Archived-At: <https://www.postgresql.org/message-id/CACxu%3DvL7i_U_iSNpREe8eCAMEyKHuPpk9THRpBhk%2Bar0U1EdOw%40mail.gmail.com>
Precedence: bulk

--0000000000001b8c700625e37ca0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, Nov 1, 2024 at 3:27=E2=80=AFPM Tom Lane <tgl@sss.pgh.pa.us> wrote:

> Michel Pelletier <pelletier.michel@gmail.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

--0000000000001b8c700625e37ca0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Fri, Nov 1, 2024 at 3:27=E2=80=AFPM To=
m Lane &lt;<a href=3D"mailto:tgl@sss.pgh.pa.us">tgl@sss.pgh.pa.us</a>&gt; w=
rote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote"=
 style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);p=
adding-left:1ex">Michel Pelletier &lt;<a href=3D"mailto:pelletier.michel@gm=
ail.com" target=3D"_blank">pelletier.michel@gmail.com</a>&gt; writes:<br><b=
r>
Here is a v1 patch series that does the first part of what we&#39;ve been<b=
r>
talking about, which is to implement the new optimization rule for<br>
the case of a single RHS reference to the target variable.=C2=A0 I&#39;m<br=
>
curious to know if it helps you at all by itself.=C2=A0 You&#39;ll definite=
ly<br>
also need commit 534d0ea6c, so probably applying these on our git<br>
master branch would be the place to start.<br></blockquote><div><br></div><=
div>I&#39;ll apply these tonight and get back to you asap.=C2=A0 There are =
many functions in my API that take only one expanded RHS argument, so I&#39=
;ll look for some cases where your changes reduce expansions when I run my =
tests.</div><div><br></div><div>Thank you!</div><div><br></div><div>-Michel=
</div></div></div>

--0000000000001b8c700625e37ca0--