Re: pg_stat_database.xact_commit + pg_stat_database.xact_rollback asa reliable metric for xid consumption ?
От | Achilleas Mantzios |
---|---|
Тема | Re: pg_stat_database.xact_commit + pg_stat_database.xact_rollback asa reliable metric for xid consumption ? |
Дата | |
Msg-id | eaded5fd-379e-1bd8-ebc6-dc85d72db4d1@matrix.gatewaynet.com обсуждение исходный текст |
Ответ на | Re: pg_stat_database.xact_commit + pg_stat_database.xact_rollback asa reliable metric for xid consumption ? (Julien Rouhaud <rjuju123@gmail.com>) |
Ответы |
Re: pg_stat_database.xact_commit + pg_stat_database.xact_rollback asa reliable metric for xid consumption ?
|
Список | pgsql-admin |
Hello Julien On 1/6/20 2:03 μ.μ., Julien Rouhaud wrote: > On Mon, Jun 1, 2020 at 12:48 PM Achilleas Mantzios > <achill@matrix.gatewaynet.com> wrote: >> On 1/6/20 1:36 μ.μ., Julien Rouhaud wrote: >>> On Mon, Jun 1, 2020 at 12:02 PM Achilleas Mantzios >>> <achill@matrix.gatewaynet.com> wrote: >>> Because read only transaction usually don't consume an xid. So yes >>> pg_stat_database gives a more reasonable approximation of the real >>> number of transactions happening on the server. >> Thank you, so what would be the official way to monitor txid consumption (from a MVCC / Freezing admin POV)? > I'm not sure what you're really looking for. I've been as explicit as it gets. When ppl talk about vacuum freeze what they have in mind is xmin's and xmax's and the ratethat xids grow and consume the 2^31 address space, so I find it strange that such a basic metric is not included in the core statistics collector. That's all. > -- Achilleas Mantzios IT DEV Lead IT DEPT Dynacom Tankers Mgmt
В списке pgsql-admin по дате отправления: