Re: Re: [COMMITTERS] pgsql: Implement current_query(), that shows the currently executing

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: [COMMITTERS] pgsql: Implement current_query(), that shows the currently executing
Date: 2008-04-05 00:47:26
Message-ID: 200804050047.m350lQX20752@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Tom Lane wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> > Bruce Momjian wrote:
> >> Alvaro Herrera wrote:
> >>> I think the agreement was that dblink_current_query was to be
> >>> implemented on top of this. In fact I don't see any reason not to.
> >>
> >> Really? It seemed like just duplicate functionality.
>
> > It's called "backwards compatibility". The nice thing about it is that
> > it doesn't cost us any extra code.
>
> Indeed. It's just silly to break dblink users when there's no need.

OK. Did someone mention this before because I don't remember it and the
patch removed the dblink usage. Do we continue to document the
function?

--
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-committers by date

  From Date Subject
Next Message Bruce Momjian 2008-04-05 01:34:06 pgsql: Have pg_stop_backup() wait for all archive files to be sent,
Previous Message Tom Lane 2008-04-05 00:40:26 Re: Re: [COMMITTERS] pgsql: Implement current_query(), that shows the currently executing

Browse pgsql-hackers by date

  From Date Subject
Next Message Brendan Jurd 2008-04-05 00:50:31 Re: Separate psql commands from arguments
Previous Message Bruce Momjian 2008-04-05 00:43:00 Re: psql \G command -- send query and output using extended format