Re: Exec statement logging - Mailing list pgsql-patches

From Tom Lane
Subject Re: Exec statement logging
Date
Msg-id 23032.1116294766@sss.pgh.pa.us
Whole thread Raw
In response to Re: Exec statement logging  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Exec statement logging  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-patches
Bruce Momjian <pgman@candle.pha.pa.us> writes:
>> What was the point again?

> Simon said that the EXECUTE is pretty useless for debugging unless we
> show the prepare query.  His patch shows the prepare query for
> client-side prepare, but not for server side when using the
> PREPARE/EXECUTE commands --- seems we should display it in both cases.

So we need to make sure that prepared statements always capture the
originating query string.  I thought you'd done that by using
debug_query_string ... which is a bit ugly but not horrid.   Why do
we need more mechanism than that?

            regards, tom lane

pgsql-patches by date:

Previous
From: Neil Conway
Date:
Subject: Re: Bunch of tab-completion enhancements for psql
Next
From: Bruce Momjian
Date:
Subject: Re: Exec statement logging