| From: | Dmitry Dolgov <9erthalion6(at)gmail(dot)com> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Changing shared_buffers without restart |
| Date: | 2024-11-08 16:40:03 |
| Message-ID: | 7tiy2lkzz3tznoosr4aqophotxm6ec46vi7g4si73ga27iw4my@qzdsgczvzzmp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On Thu, Nov 07, 2024 at 02:05:52PM GMT, Thomas Munro wrote:
> On Sat, Oct 19, 2024 at 8:21 AM Dmitry Dolgov <9erthalion6(at)gmail(dot)com> wrote:
> > Currently it
> > supports only an increase of shared_buffers.
>
> Just BTW in case it is interesting, Palak and I experimented with how
> to shrink the buffer pool while PostgreSQL is running, while we were
> talking about 13453ee (which it shares infrastructure with). This
> version fails if something is pinned and in the way of the shrink
> operation, but you could imagine other policies (wait, cancel it,
> ...):
>
> https://github.com/macdice/postgres/commit/db26fe0c98476cdbbd1bcf553f3b7864cb142247
Thanks, looks interesting. I'll try to experiment with that in the next
version of the patch.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dmitry Dolgov | 2024-11-08 16:43:06 | Re: Changing shared_buffers without restart |
| Previous Message | Tom Lane | 2024-11-08 16:26:11 | Re: not null constraints, again |