Re: [HACKERS] SCRAM in the PG 10 release notes - Mailing list pgsql-hackers

From Jeff Janes
Subject Re: [HACKERS] SCRAM in the PG 10 release notes
Date
Msg-id CAMkU=1wNE0dHo4RGAQz=qCru9H6RYuqhy=F14eDFf4Tb7ttsDg@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] SCRAM in the PG 10 release notes  (Heikki Linnakangas <hlinnaka@iki.fi>)
Responses Re: [HACKERS] SCRAM in the PG 10 release notes
Re: [HACKERS] SCRAM in the PG 10 release notes
List pgsql-hackers
On Tue, Sep 19, 2017 at 1:32 PM, Heikki Linnakangas <hlinnaka@iki.fi> wrote:
 
I'm not sure what exactly to do here. Where should we stick that notice? We could put it in the release notes, where the bullet point about SCRAM is, but it would be well hidden. If we want to give advice to people who might not otherwise pay attention, it should go to a more prominent place. In the "Migration to version 10" section perhaps. Currently, it only lists incompatibilities, which this isn't. Perhaps put the notice after the list of incompatibilities (patch attached)?


I guess I'm late to the party, but I don't see why this is needed at all.  We encourage people to use any and all new features which are appropriate to them--that is why we implement new features.  Why does this feature need a special invitation?

Cheers,

Jeff

pgsql-hackers by date:

Previous
From: Jeff Janes
Date:
Subject: Re: [HACKERS] why not parallel seq scan for slow functions
Next
From: Andreas Karlsson
Date:
Subject: Re: [HACKERS] CREATE COLLATION does not sanitize ICU's BCP 47language tags. Should it?