Re: [HACKERS] pg_stat_activity.waiting_start
От
Tom Lane
Тема
Re: [HACKERS] pg_stat_activity.waiting_start
Дата
Msg-id
8779.1482544859@sss.pgh.pa.us
Ответ на
[HACKERS] pg_stat_activity.waiting_start (Joel Jacobson)
Список
Дерево обсуждения
[HACKERS] pg_stat_activity.waiting_start Joel Jacobson <joel@trustly.com>
Re: [HACKERS] pg_stat_activity.waiting_start Tom Lane <tgl@sss.pgh.pa.us>
Re: [HACKERS] pg_stat_activity.waiting_start Stephen Frost <sfrost@snowman.net>
Re: [HACKERS] pg_stat_activity.waiting_start Tom Lane <tgl@sss.pgh.pa.us>
Re: [HACKERS] pg_stat_activity.waiting_start Amit Kapila <amit.kapila16@gmail.com>
Re: [HACKERS] pg_stat_activity.waiting_start Jim Nasby <Jim.Nasby@BlueTreble.com>
Re: [HACKERS] pg_stat_activity.waiting_start Tom Lane <tgl@sss.pgh.pa.us>
Re: [HACKERS] pg_stat_activity.waiting_start Amit Kapila <amit.kapila16@gmail.com>
Re: [HACKERS] pg_stat_activity.waiting_start Jim Nasby <Jim.Nasby@BlueTreble.com>
Re: [HACKERS] pg_stat_activity.waiting_start Tom Lane <tgl@sss.pgh.pa.us>
Re: [HACKERS] pg_stat_activity.waiting_start Robert Haas <robertmhaas@gmail.com>
Re: [HACKERS] pg_stat_activity.waiting_start Jim Nasby <Jim.Nasby@BlueTreble.com>
Re: [HACKERS] pg_stat_activity.waiting_start Joel Jacobson <joel@trustly.com>
Re: [HACKERS] pg_stat_activity.waiting_start Tom Lane <tgl@sss.pgh.pa.us>
Re: [HACKERS] pg_stat_activity.waiting_start Joel Jacobson <joel@trustly.com>
Re: [HACKERS] pg_stat_activity.waiting_start Andres Freund <andres@anarazel.de>
Re: [HACKERS] pg_stat_activity.waiting_start Joel Jacobson <joel@trustly.com>
Re: [HACKERS] pg_stat_activity.waiting_start Tom Lane <tgl@sss.pgh.pa.us>
Re: [HACKERS] pg_stat_activity.waiting_start Stephen Frost <sfrost@snowman.net>
Re: [HACKERS] pg_stat_activity.waiting_start Bruce Momjian <bruce@momjian.us>
Re: [HACKERS] pg_stat_activity.waiting_start Joel Jacobson <joel@trustly.com>
Re: [HACKERS] pg_stat_activity.waiting_start Bruce Momjian <bruce@momjian.us>
Re: [HACKERS] pg_stat_activity.waiting_start Andres Freund <andres@anarazel.de>
Re: [HACKERS] pg_stat_activity.waiting_start Greg Stark <stark@mit.edu>
Re: [HACKERS] pg_stat_activity.waiting_start Bruce Momjian <bruce@momjian.us>
Re: [HACKERS] pg_stat_activity.waiting_start Joel Jacobson <joel@trustly.com>
Re: [HACKERS] pg_stat_activity.waiting_start Jim Nasby <Jim.Nasby@BlueTreble.com>
Re: [HACKERS] pg_stat_activity.waiting_start Greg Stark <stark@mit.edu>
Re: [HACKERS] pg_stat_activity.waiting_start Jim Nasby <Jim.Nasby@BlueTreble.com>
Re: [HACKERS] pg_stat_activity.waiting_start Joel Jacobson <joel@trustly.com>
Re: [HACKERS] pg_stat_activity.waiting_start Joel Jacobson <joel@trustly.com>
Re: [HACKERS] pg_stat_activity.waiting_start Joel Jacobson <joel@trustly.com>
Joel Jacobson writes: > We already have xact_start, query_start and backend_start > to get the timestamptz for when different things happened. > I would like to propose adding a fourth such column, "waiting_start", > which would tell how long time a backend has been waiting. The difficulty with that is it'd require a gettimeofday() call for every wait start. Even on platforms where those are relatively cheap, the overhead would be nasty --- and on some platforms, it'd be astonishingly bad. We sweated quite a lot to get the overhead of pg_stat_activity wait monitoring down to the point where it would be tolerable for non-heavyweight locks, but I'm afraid this would push it back into the not-tolerable range. regards, tom lane
В списке pgsql-hackers по дате отправления