Re: "ago" times on buildfarm status page

Поиск
Список
Период
Сортировка
От Andrew Dunstan
Тема Re: "ago" times on buildfarm status page
Дата
Msg-id 41f9c12c-43cf-77d8-dfac-ec5302b3652f@2ndQuadrant.com
обсуждение исходный текст
Ответ на Re: "ago" times on buildfarm status page  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
Ответы Re: "ago" times on buildfarm status page  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
On 8/21/19 11:07 AM, Andrew Dunstan wrote:
> On 8/21/19 9:55 AM, Tom Lane wrote:
>> The real problem with that column though is that it relies on run start
>> times that are self-reported by the buildfarm clients, and some of them
>> have system clocks that are many hours off reality.  What *I'd* like to
>> see is for the column to contain time of receipt of the buildfarm report
>> at the server, less the measured runtime of the test.
>
> That might be possible. I'll put it on my list of things to do. It's not
> happening any time soon, though.
>
>


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.


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.


cheers


andrew


-- 
Andrew Dunstan                https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services




В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Removing pg_pltemplate and creating "trustable" extensions
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: pg_upgrade fails with non-standard ACL