| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: Exec statement logging |
| Date: | 2005-05-15 21:48:47 |
| Message-ID: | 1116193727.3830.507.camel@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
On Sun, 2005-05-15 at 13:29 -0400, Tom Lane wrote:
> Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> > On Sat, 2005-05-14 at 16:55 -0400, Bruce Momjian wrote:
> >> One thing you did was to log debug_query_string, but I don't see how
> >> that could be the right value.
>
> > I used the debug_query_string because even in the EXEC case it is set,
> > so that the SQL statement appears correctly in pg_stat_activity. It may
> > look wrong, but it is there.
>
> The reason debug_query_string is the right thing is that
> exec_execute_message is careful to set it up...
I realised that luck played little part and that some foreward planning
had gone into it.
Somebody out there is too modest to point out how often it is that I
only dot the "I"s they have left for me...
Best Regards, Simon Riggs
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2005-05-16 04:21:58 | Re: Exec statement logging |
| Previous Message | Tom Lane | 2005-05-15 17:29:47 | Re: Exec statement logging |