Re: [GENERAL] Upgrading using pg_dumpall [FIXED]

2016-09-04 Thread Rich Shepard
On Sun, 4 Sep 2016, Adrian Klaver wrote: I would take Charles's suggestion and set up a .pgpass file just to be safe. The file ~/.pgpass already exists, but without an explicit password. I added my password (plain text). The file already had perms 0600. Perhaps my password was rejected with

Re: [GENERAL] Upgrading using pg_dumpall [FIXED]

2016-09-04 Thread Rich Shepard
On Sun, 4 Sep 2016, Adrian Klaver wrote: Just be aware that you now have a password for the postgres user and that if you ever do enable md5 you will need it. I would take Charles's suggestion and set up a .pgpass file just to be safe. Adrian, OK. I'll also read the page at the URL you provi

Re: [GENERAL] Upgrading using pg_dumpall [FIXED]

2016-09-04 Thread Adrian Klaver
On 09/04/2016 09:01 AM, Rich Shepard wrote: On Sun, 4 Sep 2016, Adrian Klaver wrote: Actually there is an important difference. In your 9.3 file you have set METHOD set to trust and in the 9.5 file it is set to md5, which is password. Set the METHOD to trust in your 9.5 file and restart the dat

Re: [GENERAL] Upgrading using pg_dumpall [FIXED]

2016-09-04 Thread Adrian Klaver
On 09/04/2016 09:01 AM, Rich Shepard wrote: On Sun, 4 Sep 2016, Adrian Klaver wrote: Actually there is an important difference. In your 9.3 file you have set METHOD set to trust and in the 9.5 file it is set to md5, which is password. Set the METHOD to trust in your 9.5 file and restart the dat

Re: [GENERAL] Upgrading using pg_dumpall [FIXED]

2016-09-04 Thread Rich Shepard
On Sun, 4 Sep 2016, Adrian Klaver wrote: Actually there is an important difference. In your 9.3 file you have set METHOD set to trust and in the 9.5 file it is set to md5, which is password. Set the METHOD to trust in your 9.5 file and restart the database. Now for the non-socket access methods