Q: limit the length of log file entries?

From: Albrecht Dreß <albrecht(dot)dress(at)posteo(dot)de>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Q: limit the length of log file entries?
Date: 2025-09-03 15:40:45
Message-ID: YJI7DQ4I.3WYAVH2R.IWZZPYNU@AP5TCLKO.ZBA47T5B.KHWCFARS
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

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(at)test FEHLER: ungültige hexadezimale Ziffer: »r« bei Zeichen 28
albrecht(at)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.

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2025-09-03 15:56:22 Re: Q: limit the length of log file entries?
Previous Message Adrian Klaver 2025-09-01 19:02:15 Re: In-order pg_dump (or in-order COPY TO)