MIME-Version: 1.0
References: <287E4DF6-35A2-4062-AEBA-32DB1DE35C5D@leisi.net> <CANzqJaAAxnwa+KMiPDJsm=z=1g8HTskE2B2B-ZPG3SJ+=A4+=A@mail.gmail.com>
In-Reply-To: <CANzqJaAAxnwa+KMiPDJsm=z=1g8HTskE2B2B-ZPG3SJ+=A4+=A@mail.gmail.com>
From: Greg Sabino Mullane <htamfids@gmail.com>
Date: Wed, 17 Dec 2025 12:13:33 -0500
Message-ID: <CAKAnmmLLzi4eSRhj-g8JO8RFUrWwMaSmtrBSNtvqMOHCHquR+g@mail.gmail.com>
Subject: Re: Record last SELECT on a row?
To: Ron Johnson <ronljohnsonjr@gmail.com>
Cc: pgsql-general <pgsql-general@postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000ddc328064628f852"
Archived-At: <https://www.postgresql.org/message-id/CAKAnmmLLzi4eSRhj-g8JO8RFUrWwMaSmtrBSNtvqMOHCHquR%2Bg%40mail.gmail.com>
Precedence: bulk

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

On Wed, Dec 17, 2025 at 10:24=E2=80=AFAM Ron Johnson <ronljohnsonjr@gmail.c=
om>
wrote:

> pgaudit might satisfy your needs, since it would only log SELECT
> statements on that one table.  You'd still have to grep the log file, so
> the information wouldn't be real-time, but that's *probably* not
> important.
>

That would only give you table-level information, unless it was a
dirt-simple query with no joins and an easy to parse where clause.

Cheers,
Greg

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

--000000000000ddc328064628f852
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 10:24=E2=80=AFAM =
Ron Johnson &lt;<a href=3D"mailto:ronljohnsonjr@gmail.com">ronljohnsonjr@gm=
ail.com</a>&gt; wrote:</div><div class=3D"gmail_quote gmail_quote_container=
"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div d=
ir=3D"ltr">pgaudit might satisfy your needs, since it would only log SELECT=
 statements on that one table.=C2=A0 You&#39;d still have to grep the log f=
ile, so the information wouldn&#39;t be real-time, but that&#39;s <i>probab=
ly</i>=C2=A0not important.</div></div></blockquote><div><br></div><div>That=
 would only give you table-level information, unless it was a dirt-simple q=
uery with no joins and an easy to parse where clause.</div><div>=C2=A0</div=
></div><div dir=3D"ltr" class=3D"gmail_signature"><div dir=3D"ltr"><div>Che=
ers,</div><div>Greg</div><div><br></div><div>--</div><div>Crunchy Data - <a=
 href=3D"https://www.crunchydata.com" target=3D"_blank">https://www.crunchy=
data.com</a></div><div>Enterprise Postgres Software Products &amp; Tech Sup=
port</div><div><br></div></div></div></div>

--000000000000ddc328064628f852--