| From: | Rich Shepard <rshepard(at)appl-ecosys(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Upgrading using pg_dumpall |
| Date: | 2016-09-04 19:55:35 |
| Message-ID: | alpine.LNX.2.11.1609041251590.21663@localhost |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2016-09-04 20:02:31 | Re: Upgrading using pg_dumpall |
| Previous Message | Adrian Klaver | 2016-09-04 19:48:04 | Re: Upgrading using pg_dumpall |