Re: Changing shared_buffers without restart - Mailing list pgsql-hackers

From Jelte Fennema-Nio
Subject Re: Changing shared_buffers without restart
Date
Msg-id CAGECzQRNNUZsRe8MCj5g8M2=xPu-o02fGyNw_m-ZQ1qRSYzrqQ@mail.gmail.com
Whole thread Raw
In response to Re: Changing shared_buffers without restart  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Changing shared_buffers without restart
List pgsql-hackers
On Wed, 27 Nov 2024 at 22:06, Robert Haas <robertmhaas@gmail.com> wrote:
> If we had an upper bound on the size of shared_buffers

I think a fairly reliable upper bound is the amount of physical memory
on the system at time of postmaster start. We could make it a GUC to
set the upper bound for the rare cases where people do stuff like
adding swap space later or doing online VM growth. We could even have
the default be something like 4x the physical memory to accommodate
those people by default.

> reserve that amount of address space at startup time but only actually
> map a portion of it

Or is this the difficult part?



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Consider pipeline implicit transaction as a transaction block
Next
From: Peter Smith
Date:
Subject: Re: Introduce XID age and inactive timeout based replication slot invalidation