Re: [PATCHES] Implemented current_query

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Tomas Doran <bobtfish(at)bobtfish(dot)net>, Neil Conway <neilc(at)samurai(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCHES] Implemented current_query
Date: 2008-03-29 12:03:20
Message-ID: 200803291203.m2TC3KK07120@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Bruce Momjian wrote:
> Alvaro Herrera wrote:
> > Tomas Doran wrote:
> >
> > > On 28 Mar 2008, at 17:23, Bruce Momjian wrote:
> >
> > >> Perhaps we could name it received_query() to indicate it is what the
> > >> backend received and it not necessarily the _current_ query.
> > >
> > > reveived_query() sounds like a very sane name for me, and documenting it
> > > as such would allow you to expose the functionality without the possible
> > > complaints...
> >
> > client_query perhaps?
>
> Yea, that is consistent with what we do with other functions.

Uh, I think based on other usage it should be called client_statement().
Peter has us using statement instead of query in many cases.

FYI, log_statement also prints the combined query string.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message tomas 2008-03-29 12:25:21 Re: [PATCHES] Avahi support for Postgresql
Previous Message Simon Riggs 2008-03-29 08:54:13 Re: Third thoughts about the DISTINCT MAX() problem

Browse pgsql-patches by date

  From Date Subject
Next Message tomas 2008-03-29 12:25:21 Re: [PATCHES] Avahi support for Postgresql
Previous Message Heikki Linnakangas 2008-03-29 11:49:56 Re: create language ... if not exists