MIME-Version: 1.0
References: <287E4DF6-35A2-4062-AEBA-32DB1DE35C5D@leisi.net> <8567de96-062f-416a-9d19-f14abfdc925e@gelassene-pferde.biz>
In-Reply-To: <8567de96-062f-416a-9d19-f14abfdc925e@gelassene-pferde.biz>
From: Greg Sabino Mullane <htamfids@gmail.com>
Date: Wed, 17 Dec 2025 12:23:31 -0500
Message-ID: <CAKAnmmJP4LN7tJtEW7GtSJ7ztOVf3kak1TZD_8KxAakk1b0fBw@mail.gmail.com>
Subject: Re: Record last SELECT on a row?
To: Thiemo Kellner <thiemo@gelassene-pferde.biz>
Cc: pgsql-general@lists.postgresql.org
Content-Type: multipart/alternative; boundary="0000000000008ed09e0646291c70"
Archived-At: <https://www.postgresql.org/message-id/CAKAnmmJP4LN7tJtEW7GtSJ7ztOVf3kak1TZD_8KxAakk1b0fBw%40mail.gmail.com>
Precedence: bulk

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

On Wed, Dec 17, 2025 at 12:14=E2=80=AFPM Thiemo Kellner <thiemo@gelassene-p=
ferde.biz>
wrote:

> I wonder whether a view calling a set returning function would be a viabl=
e
> option. Within the function you execute the actual query twice. Once to
> merge selected pk into a protocol table and once for the return of the da=
ta
> set.
>

The view would be sucking in the entire table every time . Maybe not a big
deal as this is a very tiny table.

I think Joe wins this thread with the RLS idea however.


Cheers,
Greg

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

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

<div dir=3D"ltr"><div dir=3D"ltr">On Wed, Dec 17, 2025 at 12:14=E2=80=AFPM =
Thiemo Kellner &lt;<a href=3D"mailto:thiemo@gelassene-pferde.biz">thiemo@ge=
lassene-pferde.biz</a>&gt; wrote:</div><div class=3D"gmail_quote gmail_quot=
e_container"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px =
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
=20
 =20
=20
 <div><span dir=3D"ltr" style=3D"margin-top:0px;margin-bottom:0px">I wonder=
 whether a view calling a set returning function would be a viable option. =
Within the function you execute the actual query twice. Once to merge selec=
ted pk into a protocol table and once for the return of the data set.</span=
></div></blockquote><div><br></div><div>The view would be sucking in the en=
tire table every time . Maybe not a big deal as this is a very tiny table.<=
/div><div><br></div><div>I think Joe wins this thread with the RLS idea how=
ever.</div><div><br></div><div><br></div><div>Cheers,</div></div><div dir=
=3D"ltr" class=3D"gmail_signature"><div dir=3D"ltr"><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 Products &amp; Tech Support</div><div><br></div></div></=
div></div>

--0000000000008ed09e0646291c70--