Re: Upgrading using pg_dumpall - Mailing list pgsql-general

From Rich Shepard
Subject Re: Upgrading using pg_dumpall
Date
Msg-id alpine.LNX.2.11.1609041251590.21663@localhost
Whole thread Raw
In response to Re: Upgrading using pg_dumpall  (Adrian Klaver <adrian.klaver@aklaver.com>)
Responses Re: Upgrading using pg_dumpall
List pgsql-general
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
break it. I've other things with higher priorities.

Rich



pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: Upgrading using pg_dumpall
Next
From: Adrian Klaver
Date:
Subject: Re: Upgrading using pg_dumpall