Re: SLRUs in the main buffer pool - Page Header definitions

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Nathan Bossart <nathandbossart(at)gmail(dot)com>
Cc: "Bagga, Rishu" <bagrishu(at)amazon(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Andres Freund <andres(at)anarazel(dot)de>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, "Debnath, Shawn" <sdn(at)amazon(dot)com>, vignesh C <vignesh21(at)gmail(dot)com>
Subject: Re: SLRUs in the main buffer pool - Page Header definitions
Date: 2023-08-21 20:23:31
Message-ID: CA+TgmoYm5oYtu0SURNT-YUK6DodtfY5GAYvck_=X5xxede+TnQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Aug 18, 2023 at 12:15 PM Nathan Bossart
<nathandbossart(at)gmail(dot)com> wrote:
> I think I agree with Stephen. We routinely make changes that require
> updates to extensions, and I doubt anyone is terribly wild about
> maintaining two SLRU systems for several years.

Yeah, maintaining two systems doesn't sound like a good idea.

However, this would be a big change. I'm not sure how we validate a
change of this magnitude. There are both correctness and performance
considerations. I saw there had been a few performance results on the
thread from Thomas that spawned this thread; but I guess we'd want to
do more research. One question is: how do you decide how many buffers
to use for each SLRU, and how many to leave available for regular
data?

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2023-08-21 20:48:06 Re: Oversight in reparameterize_path_by_child leading to executor crash
Previous Message Dean Rasheed 2023-08-21 20:10:43 Re: [PATCH] Add function to_oct