| From: | Benoit Lobréau <benoit(dot)lobreau(at)dalibo(dot)com> |
|---|---|
| To: | Michael Banck <mbanck(at)gmx(dot)net> |
| Cc: | Guillaume Lelarge <guillaume(at)lelarge(dot)info>, Michael Paquier <michael(at)paquier(dot)xyz>, Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Parallel workers stats in pg_stat_database |
| Date: | 2024-11-12 17:17:52 |
| Message-ID: | 2db19fe2-0420-4ecc-8512-83acb775eeb4@dalibo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2024-11-12 17:27:37 | Re: doc: pgevent.dll location |
| Previous Message | Ranier Vilela | 2024-11-12 17:05:40 | Fix array access (src/bin/pg_dump/pg_dump.c) |