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

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

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.

> 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?

Yes, I did:

http://archives.postgresql.org/pgsql-patches/2007-05/msg00098.php

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

Browse pgsql-committers by date

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

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2008-04-05 01:46:05 Re: Re: [COMMITTERS] pgsql: Implement current_query(), that shows the currently executing
Previous Message Bruce Momjian 2008-04-05 01:34:58 Re: [HACKERS] Minor changes to Recovery related code