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

From Dmitry Dolgov
Subject Re: Changing shared_buffers without restart
Date
Msg-id 2brvipzihiad5tz4ugh4w7jjffnh53mjrvfur4e2ji5ttrkhj5@5rgbzttsq2jr
Whole thread Raw
In response to Re: Changing shared_buffers without restart  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
> On Thu, Nov 28, 2024 at 12:18:54PM GMT, Robert Haas wrote:
>
> All that having been said, what does concern me a bit is our ability
> to predict what Linux will do well enough to keep what we're doing
> safe; and also whether the Linux behavior might abruptly change in the
> future. Users would be sad if we released this feature and then a
> future kernel upgrade causes PostgreSQL to completely stop working. I
> don't know how the Linux kernel developers actually feel about this
> sort of thing, but if I imagine myself as a kernel developer, I can
> totally see myself saying "well, we never promised that this would
> work in any particular way, so we're free to change it whenever we
> like." We've certainly used that argument here countless times.

Agree, at the moment I can't say for sure how reliable this behavior is
in long term. I'll try to see if there are ways to get more confidence
about that.



pgsql-hackers by date:

Previous
From: "Andrey M. Borodin"
Date:
Subject: Re: [PATCH] Add sortsupport for range types and btree_gist
Next
From: Tom Lane
Date:
Subject: Re: Changing shared_buffers without restart