|From:||Michael Paquier <michael(at)paquier(dot)xyz>|
|To:||Julien Rouhaud <rjuju123(at)gmail(dot)com>|
|Cc:||Daymel Bonne Solís <daymelbonne(at)gmail(dot)com>, Anthony Sotolongo <asotolongo(at)gmail(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, pgsql-hackers(at)postgresql(dot)org|
|Subject:||Re: Expose Parallelism counters planned/execute in pg_stat_statements|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On Tue, Aug 16, 2022 at 02:58:43PM +0800, Julien Rouhaud wrote:
> I don't think that's an improvement. With this patch if you see the
> "paral_planned_not_exec" counter going up, you still don't know if this is
> because of the !es_use_parallel_mode or if you simply have too many parallel
> queries running at the same time, or both, and therefore can't do much with
> that information. Both situations are different and in my opinion require
> different (and specialized) counters to properly handle them.
This thread has been idle for a few weeks now, and this feedback has
not been answered to. This CF entry has been marked as RwF.
|Next Message||Amit Kapila||2022-10-12 06:04:43||Re: Perform streaming logical transactions by background workers and parallel apply|
|Previous Message||John Naylor||2022-10-12 05:57:16||Re: introduce optimized linear search functions that return index of matching element|