Tom Lane wrote: > 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?
The problem is we have to pass that string down to the completion of the query for log_min_duration_statement printing. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
