Re: [HACKERS] exposing wait events for non-backends (was: Trackingwait event for latches)
От | Robert Haas |
---|---|
Тема | Re: [HACKERS] exposing wait events for non-backends (was: Trackingwait event for latches) |
Дата | |
Msg-id | CA+TgmobYwca6tngMtB3ZG7Hv4Ar+C=g-pGuOCjH09QsTFgL_CA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] exposing wait events for non-backends (was: Trackingwait event for latches) (Michael Paquier <michael.paquier@gmail.com>) |
Ответы |
Re: [HACKERS] exposing wait events for non-backends (was: Trackingwait event for latches)
|
Список | pgsql-hackers |
On Wed, Mar 22, 2017 at 1:31 AM, Michael Paquier <michael.paquier@gmail.com> wrote: > Okay, switched as ready for committer. One note for the committer > though: keeping the calls of pgstat_bestart() out of > BackgroundWorkerInitializeConnection() and > BackgroundWorkerInitializeConnectionByOid() keeps users the > possibility to not have backends connected to the database show up in > pg_stat_activity. This may matter for some users (cloud deployment for > example). I am as well in favor in keeping the work of those routines > minimal, without touching at pgstat. I think that's just inviting bugs of omission, in both core and extension code. I think it'd be much better to do this in a centralized place. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: