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

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: bobtfish(at)bobtfish(dot)net
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, 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 02:37:38
Message-ID: 200804050237.m352bca01251@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Bruce Momjian wrote:
> I see what happened. The author said he had made the change, but the
> patch didn't contain it:
>
> http://archives.postgresql.org/pgsql-patches/2007-05/msg00132.php
> > > FWIW I think you should still provide dblink_current_query, even if it's
> > >
> > > only a wrapper over current_query(), for backwards compatibility.
> >
> > Good point. Done as suggested (I think, or did you mean also the change
> > of instances to use current_query()?). Replaced dblink_current_query
> > with an SQL procedure wrapper, I assume that's the most efficient way of
> > doing it?

I have re-added it as an undocumented dblink SQL 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. +

Attachment Content-Type Size
/rtmp/diff text/x-diff 1.4 KB

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2008-04-05 02:41:23 Re: Re: [COMMITTERS] pgsql: Implement current_query(), that shows the currently executing
Previous Message Bruce Momjian 2008-04-05 02:26:14 pgsql: Re-add dblink_current_query() for backward compatibility.

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-04-05 02:41:23 Re: Re: [COMMITTERS] pgsql: Implement current_query(), that shows the currently executing
Previous Message Tom Lane 2008-04-05 02:37:17 Re: Patch queue -> wiki