On 9/1/25 10:54, Tom Lane wrote:
Adrian Klaver writes:
I did some digging in the code and see that the TOC is more then that,
it stores a range of data. Still have not part where the offsets are
ignored for writes to stdout, but will keep on digging.
The TOC is initially written out with zero
Albrecht =?iso-8859-1?b?RHJl3w==?= writes:
> 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
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
On 9/3/25 08:40, Albrecht Dreß wrote:
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, so
