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:10:14 |
Message-ID: | alpine.LNX.2.11.1609041207240.21663@localhost |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sun, 4 Sep 2016, Adrian Klaver wrote:
> You don't it directly. That information is supplied by Postgres when you
> do CREATE or ALTER ROLE. The -W switch just does that for the
> superuser(postgres in your case) when you initdb a new cluster.
Adrian,
OK. That makes sense.
> Sorry, old habits. pg_user is a version of the pg_shadow view that blanks
> out the actual password. pg_shadow is a view over the table pg_authid,
> where the actual information is stored now. In any case, again they are
> not tables/views you directly modify.
Good. Then I won't spend time with them.
So, given my single-user situation do you think that I should ALTER ROLE
to add my password? Adding it to ~/.pgpass did nothing positive when I
changed auth method to md5; my attempt to open a database failed because
that password was rejected. Strange ... to me.
Rich
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2016-09-04 19:28:00 | Re: Upgrading using pg_dumpall |
Previous Message | Adrian Klaver | 2016-09-04 18:59:10 | Re: Upgrading using pg_dumpall |