From: | 'Bruce Momjian' <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(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:32:04 |
Message-ID: | 20170919163204.GD18066@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Sep 19, 2017 at 12:30:01PM -0400, Tom Lane wrote:
> "'Bruce Momjian'" <bruce(at)momjian(dot)us> writes:
> > On Tue, Sep 19, 2017 at 12:22:39PM -0400, Tom Lane wrote:
> >> We don't normally release-note documentation changes. If this
> >> wasn't purely a documentation change, then I was probably in error
> >> to decide it didn't need to be in the notes.
>
> > It was purely a documentation change, but it was a documented change in a
> > long-standing and popular practice of not using too many shared buffers
> > on Windows, so I thought it wise to add it.
>
> 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.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2017-09-19 16:33:52 | Re: PoC plpgsql - possibility to force custom or generic plan |
Previous Message | Tom Lane | 2017-09-19 16:30:01 | Re: PG 10 release notes |