| From: | Albrecht Dreß <albrecht(dot)dress(at)posteo(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Q: limit the length of log file entries? |
| Date: | 2025-09-04 15:48:24 |
| Message-ID: | TFULP3P6.EN64L3JH.HKBKS5SI@5MABK74K.JEDAXO5P.UTRFWLFY |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2025-09-04 15:54:07 | Re: Q: limit the length of log file entries? |
| Previous Message | Albrecht Dreß | 2025-09-04 15:48:14 | Re: Q: limit the length of log file entries? |