From: Tom Lane <tgl@sss.pgh.pa.us>
To: Justin Pryzby <pryzby@telsasoft.com>
cc: ROS Didier <didier.ros@edf.fr>, pgsql-performance@postgresql.org,
        legrand_legrand@hotmail.com
Subject: Re: How to get the content of Bind variables
In-reply-to: <20190302155638.GA29584@telsasoft.com>
References: <20190302155638.GA29584@telsasoft.com>
Comments: In-reply-to Justin Pryzby <pryzby@telsasoft.com>
	message dated "Sat, 02 Mar 2019 09:56:38 -0600"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <18363.1551544399.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Sat, 02 Mar 2019 11:33:19 -0500
Message-ID: <18364.1551544399@sss.pgh.pa.us>
Precedence: bulk

Justin Pryzby <pryzby@telsasoft.com> writes:
> On Fri, Mar 01, 2019 at 06:47:06PM +0000, ROS Didier wrote:
>> log_line_prefix =3D '%t [%p]: [%l-1] [%x] user=3D%u,db=3D%d,client=3D%h=
'

> On Sat, Mar 02, 2019 at 01:14:44PM +0000, ROS Didier wrote:
>> 2019-03-01 14:53:37 CET [24803]: [129-1] [3686] user=3Dpgbd_preint_sg2,=
db=3Dpgbd_preint_sg2 LOG:  process 24803 still waiting for ShareLock on tr=
ansaction 3711 after 1000.476 ms
>> 2019-03-01 14:53:37 CET [24803]: [130-1] [3686] user=3Dpgbd_preint_sg2,=
db=3Dpgbd_preint_sg2 DETAIL:  Process holding the lock: 24786. Wait queue:=
 24803.
>> 2019-03-01 14:53:37 CET [24803]: [131-1] [3686] user=3Dpgbd_preint_sg2,=
db=3Dpgbd_preint_sg2 CONTEXT:  while rechecking updated tuple (3,33) in re=
lation "t_shared_liste_valeurs"
>> 2019-03-01 14:53:37 CET [24803]: [132-1] [3686] user=3Dpgbd_preint_sg2,=
db=3Dpgbd_preint_sg2 STATEMENT:  update t_shared_liste_valeurs set deletio=
n_date=3D$1, deletion_login=3D$2, modification_date=3D$3, modification_log=
in=3D$4, administrable=3D$5, libelle=3D$6, niveau=3D$7 where code=3D$8

> I just realized that your log is showing "STATEMENT:  [...]" which I thi=
nk
> means that's using libpq PQexec (simple query protocol), which means it =
doesn't
> use or support bind parameters at all.

No, what's shown above is a case of the current statement being printed
as detail for some log message (a log_lock_waits message in this case).
This has nothing to do with whether statement logging is on overall.

I now realize that what the OP is probably wishing for is that bind
parameter values would be included as a detail line in messages other
than log_all_statements or statement-duration messages.  Sorry, that
feature doesn't exist, and there'd be pretty serious technical
impediments to making it happen.

			regards, tom lane