MIME-Version: 1.0
References: <CAFCRh-9SDUvcrF_RigOzXsbOm=8mHmzy2OSC1ejQNcjmfXXM_Q@mail.gmail.com>
 <CAKAnmmJeA-oXD-nOuqpi6EoSogmsgPAW-5puwN1scdc-snEC9g@mail.gmail.com> <CAFCRh-_6tqs3CF-Wf=AytJ6-_8-wq=9Tz02E7jQSk-mnRRm--w@mail.gmail.com>
In-Reply-To: <CAFCRh-_6tqs3CF-Wf=AytJ6-_8-wq=9Tz02E7jQSk-mnRRm--w@mail.gmail.com>
From: Greg Sabino Mullane <htamfids@gmail.com>
Date: Mon, 24 Feb 2025 12:36:10 -0500
Message-ID: <CAKAnmm+su9VJh5nQ3GTS88W5nJUyqFw-JrVuEj9q7mbSG0HCFw@mail.gmail.com>
Subject: Re: Keep specialized query pairs, or use single more general but more
 complex one
To: Dominique Devienne <ddevienne@gmail.com>
Cc: pgsql-general@lists.postgresql.org, andrew@tao11.riddles.org.uk
Content-Type: multipart/alternative; boundary="000000000000f19a91062ee6c854"
Archived-At: <https://www.postgresql.org/message-id/CAKAnmm%2Bsu9VJh5nQ3GTS88W5nJUyqFw-JrVuEj9q7mbSG0HCFw%40mail.gmail.com>
Precedence: bulk

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

On Mon, Feb 24, 2025 at 11:50=E2=80=AFAM Dominique Devienne <ddevienne@gmai=
l.com>
wrote:

> We lookup whether there's a list of aliases for "Allison". If there are,
> we send them in $3 as an array

of string (e.g. ['All', 'Alli', ...], and the first one matching (thanks to
> order by ord limit 1) is returned, if any.
>

Thanks, I understand it now. While the unnest will create a different plan,
it should fundamentally be the same. The join order will not matter. The
only consideration is if the unnest list grows very, very large, which
seems unlikely given your situation. And yes, it should be fine to set the
first name as the leading item in the array and only run a single query for
both cases.

As always, it's best to test on your data and your exact queries, but from
here it seems sane.

Cheers,
Greg

--
Crunchy Data - https://www.crunchydata.com
Enterprise Postgres Software Products & Tech Support

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

<div dir=3D"ltr"><div dir=3D"ltr">On Mon, Feb 24, 2025 at 11:50=E2=80=AFAM =
Dominique Devienne &lt;<a href=3D"mailto:ddevienne@gmail.com">ddevienne@gma=
il.com</a>&gt; wrote:</div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex=
">We lookup whether there&#39;s a list of aliases for &quot;Allison&quot;. =
If there are, we send them in $3 as an array</blockquote><div class=3D"gmai=
l_quote gmail_quote_container"><blockquote class=3D"gmail_quote" style=3D"m=
argin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left=
:1ex"><div dir=3D"ltr"><div class=3D"gmail_quote"><div>of string (e.g. [=
9;All&#39;, &#39;Alli&#39;, ...], and the first one matching (thanks to ord=
er by ord limit 1) is returned, if any.</div></div></div></blockquote><div>=
<br></div><div>Thanks, I understand it now. While the unnest will create a =
different=C2=A0plan, it should fundamentally be the same. The join order wi=
ll not matter. The only consideration is if the unnest list grows very, ver=
y large, which seems unlikely given your situation. And yes, it should be f=
ine to set the first name as the leading item in the array and only run a s=
ingle query for both cases.</div><div><br></div><div>As always, it&#39;s be=
st to test on your data and your exact queries, but from here it seems sane=
.</div></div><div><br></div><div dir=3D"ltr" class=3D"gmail_signature"><div=
 dir=3D"ltr"><div>Cheers,</div><div>Greg</div><div><br></div><div>--</div><=
div>Crunchy Data - <a href=3D"https://www.crunchydata.com" target=3D"_blank=
">https://www.crunchydata.com</a></div><div>Enterprise Postgres Software Pr=
oducts &amp; Tech Support</div><div><br></div></div></div></div>

--000000000000f19a91062ee6c854--