Re: PG 10 release notes

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "'Bruce Momjian'" <bruce(at)momjian(dot)us>
Cc: "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PG 10 release notes
Date: 2017-09-19 16:45:39
Message-ID: 18363.1505839539@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"'Bruce Momjian'" <bruce(at)momjian(dot)us> writes:
> On Tue, Sep 19, 2017 at 12:30:01PM -0400, Tom Lane wrote:
>> Well, if the intent of the note was to encourage people to raise
>> shared_buffers, it didn't do a very good job of that as written,
>> because I sure didn't understand it that way.

> Do you have any suggestions since it is not a code change that I can
> point to? My guess is that the limitation was removed years ago, but we
> only found out recently.

TBH, I think that's another reason for not release-noting it. There's
no concrete change to point to, and so it's hard to figure out what
to say. I'm not even very sure that we should be encouraging people
to change existing shared_buffers settings; the experiments that
Takayuki-san did were only on Windows 10, so we don't really know that
changing that would be a good idea on older Windows versions.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2017-09-19 16:47:18 Re: pgsql: Add test for postmaster crash restarts.
Previous Message Pavel Stehule 2017-09-19 16:45:09 Re: PoC plpgsql - possibility to force custom or generic plan