Re: [HACKERS] SCRAM in the PG 10 release notes

Поиск
Список
Период
Сортировка
От Jeff Janes
Тема Re: [HACKERS] SCRAM in the PG 10 release notes
Дата
Msg-id CAMkU=1wNE0dHo4RGAQz=qCru9H6RYuqhy=F14eDFf4Tb7ttsDg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [HACKERS] SCRAM in the PG 10 release notes  (Heikki Linnakangas <hlinnaka@iki.fi>)
Ответы Re: [HACKERS] SCRAM in the PG 10 release notes  (Michael Paquier <michael.paquier@gmail.com>)
Re: [HACKERS] SCRAM in the PG 10 release notes  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Список 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 по дате отправления:

Предыдущее
От: Jeff Janes
Дата:
Сообщение: Re: [HACKERS] why not parallel seq scan for slow functions
Следующее
От: Andreas Karlsson
Дата:
Сообщение: Re: [HACKERS] CREATE COLLATION does not sanitize ICU's BCP 47language tags. Should it?