Thread: Re: Changing shared_buffers without restart

Re: Changing shared_buffers without restart

From
Dmitry Dolgov
Date:
> On Fri, Oct 18, 2024 at 09:21:19PM GMT, Dmitry Dolgov wrote:
>
> TL;DR A PoC for changing shared_buffers without PostgreSQL restart, via
> changing shared memory mapping layout. Any feedback is appreciated.

It was pointed out to me, that earlier this year there was a useful
discussion about similar matters "PGC_SIGHUP shared_buffers?" [1]. From
what I see the patch series falls into the "re-map" category in that
thread.

[1]:
https://www.postgresql.org/message-id/flat/CA%2BTgmoaGCFPhMjz7veJOeef30%3DKdpOxgywcLwNbr-Gny-mXwcg%40mail.gmail.com



Re: Changing shared_buffers without restart

From
Vladlen Popolitov
Date:
Hi

I tried to apply patches, but failed. I suppose the problem with CRLF in the end of lines in the patch files. At least,
aftermanual change of v1-0001 and v1-0002 from CRLF to LF patches applied, but it was not helped for v1-0003 - v1.0005
-they have also other mistakes during patch process. Could you check patch files and place them in correct format? 

The new status of this patch is: Waiting on Author

Re: Changing shared_buffers without restart

From
Dmitry Dolgov
Date:
> On Wed, Nov 06, 2024 at 07:10:06PM GMT, Vladlen Popolitov wrote:
> Hi
>
> I tried to apply patches, but failed. I suppose the problem with CRLF in the end of lines in the patch files. At
least,after manual change of v1-0001 and v1-0002 from CRLF to LF patches applied, but it was not helped for v1-0003 -
v1.0005- they have also other mistakes during patch process. Could you check patch files and place them in correct
format?
>
> The new status of this patch is: Waiting on Author

Well, I'm going to rebase the patch if that's what you mean. But just
FYI -- it could be applied without any issues to the base commit
mentioned in the series.