| From: | Kasahara Tatsuhito <kasahara(dot)tatsuhito(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #13979: Strange pg_stat_statements results with PREPARE/EXECUTE |
| Date: | 2016-02-24 18:05:12 |
| Message-ID: | CAP0=ZVJ1Sc6tF8rfvFEOYV_3wU32NsdxvgueevV=3mN0ZOWcHg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi,
2016-02-24 0:38 GMT+09:00 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ranier VF | 2016-02-24 19:03:27 | Re: BUG #13980: UNINITIALIZED READ |
| Previous Message | Kasahara Tatsuhito | 2016-02-24 17:53:05 | Re: BUG #13979: Strange pg_stat_statements results with PREPARE/EXECUTE |