Skip site navigation (1) Skip section navigation (2)

Re: Exec statement logging

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-patches(at)postgresql(dot)org
Subject: Re: Exec statement logging
Date: 2005-05-14 21:57:52
Message-ID: 6949.1116107872@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-patches
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> One thing you did was to log debug_query_string, but I don't see how
> that could be the right value.  I assume it would be empty in a
> client-side execute, or be the previous query.  I instead used "EXECUTE
> portal_name" because that is what we are passed from the client.

You could use portal->sourceText whenever that isn't null; it should be
the querystring that the portal was created by.

			regards, tom lane

In response to

Responses

pgsql-patches by date

Next:From: S Murthy KambhampatyDate: 2005-05-14 23:00:45
Subject: Config option log_statement
Previous:From: Andrew DunstanDate: 2005-05-14 21:14:14
Subject: Re: [HACKERS] plperl and pltcl installcheck targets

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group