Horton
Menu

Re: Parallel workers stats in pg_stat_database

Benoit Lobréau <benoit.lobreau@dalibo.com>

View thread
From: Benoit Lobréau <benoit.lobreau@dalibo.com>
To: Michael Banck <mbanck@gmx.net>
Cc: Guillaume Lelarge <guillaume@lelarge.info>, Michael Paquier <michael@paquier.xyz>, Bertrand Drouvot <bertranddrouvot.pg@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2024-11-12T17:17:52Z
Lists: pgsql-hackers 

On 11/12/24 16:24, Michael Banck wrote:
> I am not sure "backend state" is a good reason (unless it is exposed
> somewhere to users?), but the point about utilities does make sense I
> guess.

We only track parallel workers used by queries right now.

Parallel index builds (btree & brin) and vacuum cleanup is not commited 
yet since it's not a common occurence. I implemented it in separate
counters.

-- 
Benoit Lobréau
Consultant
http://dalibo.com

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Add two attributes to pg_stat_database for parallel workers activity

  2. Introduce two fields in EState to track parallel worker activity