Re: PostgreSQL Log Info

From: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
To: "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: PostgreSQL Log Info
Date: 2024-11-22 09:07:44
Message-ID: CANzqJaBHN3wt2pdwqLEhaaJ4CgQVg7+_5Vwjk2DNP89OQSh+AQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Isn't "I need the query returned values" the purpose of the client
application?

On Fri, Nov 22, 2024 at 2:32 AM Jethish Jethish <jethish777(at)gmail(dot)com>
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
>
> On Fri, Nov 22, 2024, 10:49 AM David G. Johnston <
> david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
>> On Thursday, November 21, 2024, Jethish Jethish <jethish777(at)gmail(dot)com>
>> wrote:
>>>
>>> Is it possible to log the rows returned by a query in the PostgreSQL
>>> logs?
>>>
>>
>> As a practical matter, no. That said, given one can get row contents
>> into the server log in various ways, what is the use case for why this
>> capability is thought to be needed?
>>
>> David J.
>>
>

--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Matthias Apitz 2024-11-22 09:10:29 Re: CVE-2024-10979 Vulnerability Impact on PostgreSQL 11.10
Previous Message Achilleas Mantzios - cloud 2024-11-22 09:01:29 Re: CVE-2024-10979 Vulnerability Impact on PostgreSQL 11.10