public inbox for [email protected]  

help / color / mirror / Atom feed

From: Albrecht Dreß <[email protected]>
To: [email protected]
Subject: Q: limit the length of log file entries?
Date: Wed, 03 Sep 2025 15:40:45 +0000
Message-ID: <[email protected]> (raw)

Hi all,

I wonder if it would be possible to limit the length of individual log lines being written to the log file.

Background:
I have a PL/PGsql DB function 'addval(_id text, _data bytea) RETURNS VOID'.  When a broken bytea is passed as 2nd parameter, something like

albrecht@test FEHLER:  ungültige hexadezimale Ziffer: »r« bei Zeichen 28
albrecht@test ANWEISUNG:  SELECT FROM addval('hopp', '\xbroken')

is printed in the log file.  This is fine and very helpful in this case, but I have a “friendly user” who transmitted a broken hex string of ~100 KBytes as second parameter, resulting in a log line of this size which is not really readable and when done frequently quickly fills the logs.

The log settings are, inter alia

log_parameter_max_length = 256
log_parameter_max_length_on_error = 256
log_error_verbosity = TERSE

but seem to have not the desired effect in this case.

I use PostgreSQL version 17.6-1.pgdg13+1 on Debian Trixie.

Thanks in advance for any help,
Albrecht.

Attachments:

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

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]
  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