Re: BUG #13979: Strange pg_stat_statements results with PREPARE/EXECUTE - Mailing list pgsql-bugs

From Kasahara Tatsuhito
Subject Re: BUG #13979: Strange pg_stat_statements results with PREPARE/EXECUTE
Date
Msg-id CAP0=ZVJ1Sc6tF8rfvFEOYV_3wU32NsdxvgueevV=3mN0ZOWcHg@mail.gmail.com
Whole thread Raw
In response to Re: BUG #13979: Strange pg_stat_statements results with PREPARE/EXECUTE  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Hi,

2016-02-24 0:38 GMT+09:00 Tom Lane <tgl@sss.pgh.pa.us>:
> What's in the query field is whatever source string the query was created
> from.  In the case of a prepared statement, we could potentially show
> either the PREPARE or the EXECUTE, but the former was deemed much more
> useful.  There's no logic in there to invent a string that was never
> actually submitted to the engine.
Thanks for your explanation.
I got it.

Anyway in the real cases, I think we would not encounter those
case(like my samples) so much.
--
Tatsuhito Kasahara
kasahara.tatsuhito _at_ gmail.com

pgsql-bugs by date:

Previous
From: Kasahara Tatsuhito
Date:
Subject: Re: BUG #13979: Strange pg_stat_statements results with PREPARE/EXECUTE
Next
From: Alvaro Herrera
Date:
Subject: Re: BUG #13985: Segmentation fault on PREPARE TRANSACTION