Re: increase size of pg_commit_ts buffers - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: increase size of pg_commit_ts buffers
Date
Msg-id CA+hUKG+zUv0XPdM53YVmAUOVi6sj+VbdrF1UubS=JA_ULWyNtg@mail.gmail.com
Whole thread Raw
In response to Re: increase size of pg_commit_ts buffers  (Andrey Borodin <x4mmm@yandex-team.ru>)
Responses Re: increase size of pg_commit_ts buffers  (Tomas Vondra <tomas.vondra@enterprisedb.com>)
List pgsql-hackers
On Mon, Feb 15, 2021 at 11:56 PM Andrey Borodin <x4mmm@yandex-team.ru> wrote:
> > 16 янв. 2021 г., в 03:07, Alvaro Herrera <alvherre@alvh.no-ip.org> написал(а):
> > Andrey Borodin already has a patch to change the behavior for
> > multixact, which is something we should perhaps also do.  I now notice
> > that they're also reporting a bug in that thread ... sigh
>
> I've tried in that thread [0] to do more intelligent optimisation than just increase number of buffers.
> Though, in fact bigger memory had dramatically better effect that lock tricks.
>
> Maybe let's make all SLRUs buffer sizes configurable?

+1

I got interested in the SLRU sizing problem (the lock trick and CV
stuff sounds interesting too, but I didn't have time to review that in
this cycle).  The main problem I'm aware of with it is the linear
search, so I tried to fix that.  See Andrey's thread for details.



pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: [UNVERIFIED SENDER] Re: Challenges preventing us moving to 64 bit transaction id (XID)?
Next
From: Kyotaro Horiguchi
Date:
Subject: Re: Get memory contexts of an arbitrary backend process