On Tue, Jul 20, 2021 at 05:04:19PM +1200, David Rowley wrote:
> On Mon, 12 Jul 2021 at 19:23, David Rowley <dgrowleyml@gmail.com> wrote:
> > I also adjusted the hash seq scan code so that it performs better when
> > faced a non-sparsely populated table. Previously my benchmark for
> > that case didn't do well [2].
>
> I was running some select only pgbench tests today on an AMD 3990x
> machine with a large number of processes.
>
> I saw that LockReleaseAll was coming up on the profile a bit at:
This last update was two months ago, and the patch has not moved
since:
https://commitfest.postgresql.org/34/3220/
Do you have plans to work more on that or perhaps the CF entry should
be withdrawn or RwF'd?
--
Michael