From: | Greg Stark <gsstark(at)mit(dot)edu> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: time-delayed standbys |
Date: | 2011-04-20 14:25:09 |
Message-ID: | BANLkTimTm48ZKYrj4jGDCYuqWBUqZb+q2Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Apr 20, 2011 at 3:19 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> My idea of how to manage it would be to have walreceiver explicitly
> track the clock difference from the master, which it can do since
> walsender puts its current time into every message header. You can use
> the slave's clock for comparisons so long as you add the appropriate
> offset. (The theory here is that the skew won't change very fast ...)
>
Ah, so we did put the master's clock in every message? Then this
should be simple, no? Just compare the master's timestamp from the
record to the last master's clock seen in the messages. That sounds
equivalent but a lot safer than trying to keep a conversion between
them.
--
greg
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-04-20 14:35:53 | Re: REINDEX vs broken HOT chains, redux |
Previous Message | Greg Stark | 2011-04-20 14:20:27 | Re: REINDEX vs broken HOT chains, redux |