Feedback-ID: i76984098:Fastmail
Message-ID: <a02b1b2e-e35b-4cf0-8888-84bbc6816ff6@aklaver.com>
Date: Thu, 4 Sep 2025 08:54:07 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Q: limit the length of log file entries?
To: =?UTF-8?Q?Albrecht_Dre=C3=9F?= <albrecht.dress@posteo.de>,
 Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-general@lists.postgresql.org
References: <TFULP3P6.EN64L3JH.HKBKS5SI@5MABK74K.JEDAXO5P.UTRFWLFY>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <TFULP3P6.EN64L3JH.HKBKS5SI@5MABK74K.JEDAXO5P.UTRFWLFY>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://www.postgresql.org/message-id/a02b1b2e-e35b-4cf0-8888-84bbc6816ff6%40aklaver.com>
Precedence: bulk

On 9/4/25 08:48, Albrecht Dreß wrote:
> Am 03.09.25 21:07 schrieb(en) Tom Lane:
>> There isn't any provision for limiting the length of source queries
>> quoted in the log.
> 
> I see, thanks for the clarification.  IMHO, it would be nice to have such an option, though…
> 
>> Had your user sent the bytea value as a query
>> parameter, then log_parameter_max_length[_on_error] would have
>> applied, but this looks like the value was just inline in the query.
> 
> I can confirm that the limitation is applied when I call PQexecParams() from a little c test application with the data included in the paramValues array.  The overlong log lines result from queries in a Python script using the psycopg2 module – no idea how this component formats the query.

The best explanation is found from the psycopg(3) docs:

https://www.psycopg.org/psycopg3/docs/basic/from_pg2.html

Differences from psycopg2

"Psycopg 3 sends the query and the parameters to the server separately, 
instead of merging them on the client side. Server-side binding works 
for normal SELECT and data manipulation statements (INSERT, UPDATE, 
DELETE), but it doesn’t work with many other statements. For instance, 
it doesn’t work with SET or with NOTIFY:"


> 
> Thanks again,
> Albrecht.


-- 
Adrian Klaver
adrian.klaver@aklaver.com