public inbox for [email protected]  

help / color / mirror / Atom feed

From: Albrecht Dreß <[email protected]>
To: Tom Lane <[email protected]>
Cc: [email protected]
Subject: Re: Q: limit the length of log file entries?
Date: Thu, 04 Sep 2025 15:48:24 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

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.

Thanks again,
Albrecht.

Attachments:

  [application/pgp-signature] openpgp-digital-signature.asc (488B, 2-openpgp-digital-signature.asc)
  download

view thread (2+ messages)

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Q: limit the length of log file entries?
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox