| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: archive_keepalive_command |
| Date: | 2012-03-28 13:49:40 |
| Message-ID: | CA+TgmoYZfTp=OSsw1osri5EQwTEHrObbooTSMSKpvt3d_FTh7A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Mar 5, 2012 at 11:55 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On Sun, Mar 4, 2012 at 1:20 AM, Jeff Janes <jeff(dot)janes(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2012-03-28 13:51:54 | Re: Should I implement DROP INDEX CONCURRENTLY? |
| Previous Message | Robert Haas | 2012-03-28 13:47:02 | Re: Review of pg_archivecleanup -x option patch |