Re: How to log bind values for statements that produce errors

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Raul Kaubi <raulkaubi(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: How to log bind values for statements that produce errors
Date: 2021-09-07 13:48:52
Message-ID: 3168996.1631022532@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Raul Kaubi <raulkaubi(at)gmail(dot)com> writes:
> We have a problem with certain select statement, which produces error and we would like to know the bind value that is given as parameter.
> I have tried parameters:
> log_min_duration_statement = 0
> log_parameter_max_length_on_error = -1

The other constraint on reporting parameters during error is that they
have to be sent by the client in text not binary mode. I venture that
your client is sending them in binary.

(The reason for this restriction is to avoid the overhead of converting
binary to text for every query, which we'd have to do in advance of
knowing whether the query will throw an error.)

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Raul Kaubi 2021-09-07 14:52:52 Re: How to log bind values for statements that produce errors
Previous Message Philippe Doussot 2021-09-07 11:59:19 Re: update non-indexed value is slow if some non-related index/fk are enabled