RE: Changing shared_buffers without restart

2025-07-15 Thread Jack Ng
>> On Mon, Jul 14, 2025 at 03:18:10PM +, Jack Ng wrote: >> Just brain-storming here... would moving NBuffers to shared memory solve >this specific issue? Though I'm pretty sure that would open up a new set of >synchronization issues elsewhere, so I'm not sure if th

RE: Changing shared_buffers without restart

2025-07-14 Thread Jack Ng
Freund >Sent: Monday, July 14, 2025 11:12 AM >To: Dmitry Dolgov <9erthali...@gmail.com> >Cc: Thom Brown ; Ashutosh Bapat >; Tomas Vondra ; >Thomas Munro ; PostgreSQL-development hack...@postgresql.org>; Jack Ng ; Ni Ku > >Subject: Re: Changing shared_buffers without

RE: Changing shared_buffers without restart

2025-07-14 Thread Jack Ng
>To: Dmitry Dolgov <9erthali...@gmail.com> >Cc: Thom Brown ; Ashutosh Bapat >; Tomas Vondra ; >Thomas Munro ; PostgreSQL-development hack...@postgresql.org>; Jack Ng ; Ni Ku > >Subject: Re: Changing shared_buffers without restart > >Hi, > >On 2025-07-14 16:0

RE: Changing shared_buffers without restart

2025-05-12 Thread Jack Ng
ming! > I thought I had shared a test program upthread, but I don't find it now. > Attached here. Can you please share your test program? Sure, mine is attached here (it’s based on another test program you shared before :-) Regards, Jack Ng #define _GNU_SOURCE #include #include

RE: Changing shared_buffers without restart

2025-05-06 Thread Jack Ng
both expand and shrink seem to work as expected --for shrink, the memory is freed right after the resize ftruncate. Regards, Jack Ng

RE: Changing shared_buffers without restart

2025-05-05 Thread Jack Ng
n SHMEM_RESIZE_RATIO to ensure the reserved space of those segments are sufficient. Regards, Jack Ng -Original Message- From: Dmitry Dolgov <9erthali...@gmail.com> Sent: Monday, April 21, 2025 5:33 AM To: Ni Ku Cc: Ashutosh Bapat ; pgsql-hack...@postgresql.org; Robert Haas