| From: | hubert depesz lubaczewski <depesz(at)depesz(dot)com> |
|---|---|
| To: | Jethish Jethish <jethish777(at)gmail(dot)com> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: PostgreSQL Log Info |
| Date: | 2024-11-22 11:25:44 |
| Message-ID: | Z0BqOL2dGd9oCqiy@depesz.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Nov 22, 2024 at 01:02:27PM +0530, Jethish Jethish wrote:
> Hi David,
>
> If an select query is fired I need the query returned values needs to be
> logged in my PostgreSQL log file.
>
>
> For example if a select query returns 5 rows I need the same in the log
> file
Please note that you wrote what you want to do. And David asked about
use case. Which is different.
Basically the question can be summed into: *why* you think you want
that.
I don't think anything even remotely similar to this exists. You could,
of course, add it to Pg by changing sources (it is open source after
all), but given that such feature would be downright dangerous for huge
majority of situations, I don't expect it to become reality in mainline
Pg.
Best regards,
depesz
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karsten Hilbert | 2024-11-22 11:35:55 | Re: PostgreSQL Log Info |
| Previous Message | Ron Johnson | 2024-11-22 09:18:02 | Re: CVE-2024-10979 Vulnerability Impact on PostgreSQL 11.10 |