| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Cc: | Noah Misch <noah(at)leadboat(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Andreas Karlsson <andreas(at)proxel(dot)se>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: SCRAM in the PG 10 release notes |
| Date: | 2017-09-19 21:55:52 |
| Message-ID: | CAMkU=1wNE0dHo4RGAQz=qCru9H6RYuqhy=F14eDFf4Tb7ttsDg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Sep 19, 2017 at 1:32 PM, Heikki Linnakangas <hlinnaka(at)iki(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Karlsson | 2017-09-19 22:23:10 | Re: CREATE COLLATION does not sanitize ICU's BCP 47 language tags. Should it? |
| Previous Message | Jeff Janes | 2017-09-19 21:35:56 | Re: why not parallel seq scan for slow functions |