"Immediate shutdown if postmaster.pid is removed" not mentioned in Release Notes

I noticed, that 9.5 release notes (beta2) do not mention
commit 7e2a18a9161fee7e67642863f72b51d77d3e996.

I think this one should be added.

+1.

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Victor Yegorov <vyegorov@gmail.com> writes:

I noticed, that 9.5 release notes (beta2) do not mention
commit 7e2a18a9161fee7e67642863f72b51d77d3e996.

We don't normally document back-patched patches in as-yet-unreleased
branches, since the point of release notes is to tell you what's new
compared to the previous release, and this item isn't (or won't be).

Also, I doubt that this is of any great concern to the average user.
It's not a scenario that would come up in anything I would call a
supported use-case. If we're to reverse the aforementioned policy,
there are probably quite a few patches that would now need to be
documented as "new in 9.5" and are more significant than this.

regards, tom lane

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

On Wed, Dec 16, 2015 at 3:42 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

Victor Yegorov <vyegorov@gmail.com> writes:

I noticed, that 9.5 release notes (beta2) do not mention
commit 7e2a18a9161fee7e67642863f72b51d77d3e996.

We don't normally document back-patched patches in as-yet-unreleased
branches, since the point of release notes is to tell you what's new
compared to the previous release, and this item isn't (or won't be).

Also, I doubt that this is of any great concern to the average user.
It's not a scenario that would come up in anything I would call a
supported use-case. If we're to reverse the aforementioned policy,
there are probably quite a few patches that would now need to be
documented as "new in 9.5" and are more significant than this.

​IOW, if you are familiar with how a previous version works you should keep
up with its release notes to catch a bug-fix behavior change like this.
Those who will end up learning on the upcoming release will simply learn
that this is how things work.

David J.
​

We don't normally document back-patched patches in as-yet-unreleased
branches, since the point of release notes is to tell you what's new
compared to the previous release, and this item isn't (or won't be).

That makes sense.

Also, I doubt that this is of any great concern to the average user.
It's not a scenario that would come up in anything I would call a
supported use-case. If we're to reverse the aforementioned policy,
there are probably quite a few patches that would now need to be
documented as "new in 9.5" and are more significant than this.

It's possible that novice admins accidentally remove postmaster.pid (I
saw this kind of incidents a few times while supporting customers if
my memory serves). Anyway I am happy as long as it's clearly
documented in the release notes of the next versions.

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general