Logging parameters values on bind error - Mailing list pgsql-hackers

From Jehan-Guillaume de Rorthais
Subject Logging parameters values on bind error
Date
Msg-id 5072FDC8.9070706@dalibo.com
Whole thread Raw
Responses Re: Logging parameters values on bind error  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

We were struggling today with some java code binding values violating
some constraints in a prepared statement.

We don't own the code and couldn't make tests with it. So we tried to
find if PostgreSQL was able to log binded values when the BIND
operation fail and found that this is not possible in current release:
the error raised while planing the statement is not caught.

PFA a patch that catch any error while creating the query plan and add
parameters values to the error message if log_statement or
log_min_duration_statement would have logged it.

Comments?
- --
Jehan-Guillaume de Rorthais
http://www.dalibo.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlBy/cgACgkQXu9L1HbaT6Li5QCdEa9Zc4g302znpHmrwB9dnRBI
JSwAnR2Poil0QAP6b+TflM2ebDCPLq3G
=HU3H
-----END PGP SIGNATURE-----

Attachment

pgsql-hackers by date:

Previous
From: Jeff Janes
Date:
Subject: Re: Warnings from fwrite() in git head
Next
From: Pavel Stehule
Date:
Subject: Re: why can't plpgsql return a row-expression?