| From: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: "ago" times on buildfarm status page |
| Date: | 2019-08-23 13:21:59 |
| Message-ID: | 485298a5-e5bb-2e60-9a14-16c135588482@2ndQuadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 8/21/19 4:16 PM, Tom Lane wrote:
> Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> writes:
>> What I have done quickly is to store a measure of the clock skew. We
>> already calculated it but we didn't store it. Initial indications are
>> that only a few have significant skew.
> Oh, I didn't know that the server had the ability to measure that.
>
> (Yes, I agree that there are just a couple with big skews at any
> one time.)
>
>> Still, if we simply added the skew to the snapshot time that might be
>> enough to achieve what you want. That would be a one line change, I think.
> +1
>
>
Done. It's only happening prospectively, so we'll need to wait a few
days to see it flow through.
cheers
andrew
--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2019-08-23 13:28:25 | Re: [Proposal] Table-level Transparent Data Encryption (TDE) and Key Management Service (KMS) |
| Previous Message | Ibrar Ahmed | 2019-08-23 13:03:10 | Re: WIP/PoC for parallel backup |