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

From: Tatsuo Ishii <ishii(at)postgresql(dot)org>
To: tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: vyegorov(at)gmail(dot)com, pgsql-general(at)postgresql(dot)org
Subject: Re: "Immediate shutdown if postmaster.pid is removed" not mentioned in Release Notes
Date: 2015-12-17 00:15:20
Message-ID: 20151217.091520.538619560850413420.t-ishii@sraoss.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> 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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Stephen Frost 2015-12-17 00:31:15 Re: Check old and new tuple in row-level policy?
Previous Message Karl Czajkowski 2015-12-16 23:15:04 Check old and new tuple in row-level policy?