Re: Changing shared_buffers without restart

From: Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Changing shared_buffers without restart
Date: 2024-11-27 21:28:06
Message-ID: CAGECzQRNNUZsRe8MCj5g8M2=xPu-o02fGyNw_m-ZQ1qRSYzrqQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 27 Nov 2024 at 22:06, Robert Haas <robertmhaas(at)gmail(dot)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?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2024-11-27 21:37:47 Re: Introduce XID age and inactive timeout based replication slot invalidation
Previous Message Bruce Momjian 2024-11-27 21:20:10 Re: Consider pipeline implicit transaction as a transaction block