Re: RFC: replace pg_stat_activity.waiting with something more descriptive

Поиск
Список
Период
Сортировка
От Peter Geoghegan
Тема Re: RFC: replace pg_stat_activity.waiting with something more descriptive
Дата
Msg-id CAM3SWZRwo6i0gminoLugvfsnuBksdXuBW60wwHf_QXxsC-Xv0w@mail.gmail.com
обсуждение исходный текст
Ответ на Re: RFC: replace pg_stat_activity.waiting with something more descriptive  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: RFC: replace pg_stat_activity.waiting with something more descriptive  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Дерево обсуждения 
On Tue, Jul 14, 2015 at 7:25 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> FWIW, I entirely share Robert's opinion that adding gettimeofday()
> overhead in routinely-taken paths is likely not to be acceptable.

I think that it can depend on many factors. For example, the
availability of vDSO support on Linux/glibc.

I've heard that clock_gettime() with CLOCK_REALTIME_COARSE, or with
CLOCK_MONOTONIC_COARSE can have significantly lower overhead than
gettimeofday().
-- 
Peter Geoghegan

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

Предыдущее
От: Fujii Masao
Дата:
Сообщение: Re: Re: [COMMITTERS] pgsql: Map basebackup tablespaces using a tablespace_map file
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Bugs in our qsort implementation