| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Christoph Berg <myon(at)debian(dot)org>, Devrim Gündüz <devrim(at)gunduz(dot)org>, Craig Ringer <craig(at)2ndquadrant(dot)com>, pgsql-pkg-yum <pgsql-pkg-yum(at)postgresql(dot)org> |
| Subject: | Re: Can we stop defaulting to 'ident'? |
| Date: | 2020-05-20 22:36:30 |
| Message-ID: | 074a1634-450f-1e2f-53aa-178de3ac1076@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-pkg-debian pgsql-pkg-yum |
On 2020-05-20 17:33, Stephen Frost wrote:
>> But this leads to other questions, like, what should pg_upgrade do?
> Same as it always has- make the user deal with anything they need to
> regarding postgresql.conf? Why would anything change with pg_upgrade?
Well, one might expect that the user at least gets some kind of
notification that something is changing. What happens when you end up
with a mix of MD5 and SCRAM passwords in pg_authid? Are users going to
be notified about this somehow? Has this been thought through to the
end? Have all combinations been tested?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2020-05-20 23:00:27 | Re: Can we stop defaulting to 'ident'? |
| Previous Message | Stephen Frost | 2020-05-20 16:35:09 | Re: Can we stop defaulting to 'ident'? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2020-05-20 23:00:27 | Re: Can we stop defaulting to 'ident'? |
| Previous Message | Peter Eisentraut | 2020-05-20 22:31:49 | Re: Removing PL/Python2 from PostgreSQL 13 |