Re: archive_keepalive_command - Mailing list pgsql-hackers

From Robert Haas
Subject Re: archive_keepalive_command
Date
Msg-id CA+TgmoYZfTp=OSsw1osri5EQwTEHrObbooTSMSKpvt3d_FTh7A@mail.gmail.com
Whole thread Raw
In response to Re: archive_keepalive_command  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
On Mon, Mar 5, 2012 at 11:55 AM, Simon Riggs <simon@2ndquadrant.com> wrote:
> On Sun, Mar 4, 2012 at 1:20 AM, Jeff Janes <jeff.janes@gmail.com> wrote:
>> Does this patch have any user-visible effect?  I thought it would make
>> pg_last_xact_replay_timestamp() advance, but it does not seem to.  I
>> looked through the source a bit, and as best I can tell this only sets
>> some internal state which is never used, except under DEBUG2
>
> Thanks for the review. I'll look into that.

Simon, are you still hoping to get this done for this releases?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Review of pg_archivecleanup -x option patch
Next
From: Robert Haas
Date:
Subject: Re: Should I implement DROP INDEX CONCURRENTLY?