| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Petr Jelinek <petr(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Jaime Casanova <jaime(at)2ndquadrant(dot)com> |
| Subject: | Re: tracking commit timestamps |
| Date: | 2014-11-11 16:10:47 |
| Message-ID: | CA+U5nMLa5H5tOBoT+23cv+N=L3qPZj1ZkEvbyHf0+AVYLSOAMQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-www |
On 4 November 2014 08:23, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
>> 6) Shouldn't any value update of track_commit_timestamp be tracked in
>> XLogReportParameters? That's thinking about making the commit timestamp
>> available on standbys as well..
>
> Yes, it should.
Agree committs should be able to run on standby, but it seems possible
to do that without it running on the master. The two should be
unconnected.
Not sure why we'd want to have parameter changes on master reported?
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-11-11 16:12:20 | Re: 9.4RC1 next week |
| Previous Message | Andres Freund | 2014-11-11 16:01:15 | Re: 9.4RC1 next week |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-11-11 16:19:02 | Re: tracking commit timestamps |
| Previous Message | Steve Singer | 2014-11-10 16:58:12 | Re: tracking commit timestamps |