Re: Upgrading using pg_dumpall
От | Adrian Klaver |
---|---|
Тема | Re: Upgrading using pg_dumpall |
Дата | |
Msg-id | b3bc7848-f20f-1223-786f-eaf62a6acacb@aklaver.com обсуждение исходный текст |
Ответ на | Re: Upgrading using pg_dumpall (Rich Shepard <rshepard@appl-ecosys.com>) |
Список | pgsql-general |
On 09/04/2016 12:55 PM, Rich Shepard wrote: > On Sun, 4 Sep 2016, Adrian Klaver wrote: > >> Another thing that came to mind is compatibility with existing >> applications/clients. You say you have been running using trust and I am >> betting your client connection parameters reflect that. Now for >> connections methods that can 'see' the .pgpass file and use libpq as the >> their underlying Postgres library then things should work. Otherwise your >> applications may not be able to connect until you supply the correct >> password in some manner. > > That's a concern. My business financial software uses postgres as the > backend and a browser UI and I enter my username and password on the login > page. It works with auth method trust. I've no idea exactly how it connects > to the database. Since it ain't broke I won't futz with it and possibly It is using its own authentication method and tables, independent of Postgres, that restrict access to its own data, not the cluster as whole. > break it. I've other things with higher priorities. > > Rich > > > -- Adrian Klaver adrian.klaver@aklaver.com
В списке pgsql-general по дате отправления: