From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Claudio Freire <klaussfreire(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PG 10 release notes |
Date: | 2017-04-25 17:39:07 |
Message-ID: | 20170425173907.GW7513@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Apr 25, 2017 at 02:31:50PM -0300, Claudio Freire wrote:
> >> Author: Álvaro Herrera, loosely based on a submission by Claudio Freire
> >> Discussion:
> >> https://postgr.es/m/CAGTBQpa6NFGO_6g_y_7zQx8L9GcHDSQKYdo1tGuh791z6PYgEg@mail.gmail.com
> >
> > I don't think this warrants inclusion in the release notes for reasons
> > already discussed. The vacuum truncation operation is a rare one and
> > an implementation detail.
>
> \_(0_0)_/
>
> As you wish.
>
> Though if I wasn't already aware of it, I would like to know, because
> it's been a source of trouble in the past.
Understood, but the question is whether the release notes are the right
place to educate users of something that will no longer be a problem. I
am happy to adjust things to whatever the community wants, but, on the
other hand I have a responsibility to be consistent what what they have
wanted in the past. I am also open to reviewing how we filter things
compared other projects.
On a larger note, not being in the release notes doesn't mean it isn't
important, but rather, that is isn't a change users need to know about.
--
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 | Tom Lane | 2017-04-25 17:44:09 | Re: PG 10 release notes |
Previous Message | Andres Freund | 2017-04-25 17:37:48 | Re: PG 10 release notes |