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

Hmm, actually, this same client executes several queries for that same session. For the first queries, I can clearly see the binds in postgresql.log. Only this third query that is being executed, it produces error and not binds are logged. Also, there may the case, where the third query gets its bi

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

Raul Kaubi 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

How to log bind values for statements that produce errors

H Centos7, postgres 13 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. At the moment, the column is bigint type, and probably the bind that goes there is text, in postgresql logfile, the error is followin