On 16/10/13, Tom Lane (t...@sss.pgh.pa.us) wrote:
> Rory Campbell-Lange writes:
> > 2013-10-16 16:21:16 BST template1 LOG: local user with ID does
> > not exist
> > 2013-10-16 16:21:16 BST template1 FATAL: Peer authentication failed
> > for user "postgres"
>
> > However /etc/passwd h
On 10/16/2013 8:34 AM, Rory Campbell-Lange wrote:
I've just turned the setting in pg_hba.conf from md5 back to peer and
reloaded the server so that it now reads as:
local all postgrespeer
Attempting to log in fails with the following error on t
Rory Campbell-Lange writes:
> Thanks for the suggestion for checking the logs. My apologies for not
> checking that. The logs show:
> 2013-10-16 16:21:16 BST template1 LOG: local user with ID does not
> exist
> 2013-10-16 16:21:16 BST template1 FATAL: Peer authentication failed for
>
On 16/10/13, Adrian Klaver (adrian.kla...@gmail.com) wrote:
> On 10/16/2013 06:56 AM, Rory Campbell-Lange wrote:
> >I have just done an update on my Debian servers running postgresql 9.2
> >(Postgres is from 9.2.4-2.pgdg70+1 from apt.postgresql.org) and suddenly
> >can't login to postgresql as post
On 10/16/2013 06:56 AM, Rory Campbell-Lange wrote:
I have just done an update on my Debian servers running postgresql 9.2
(Postgres is from 9.2.4-2.pgdg70+1 from apt.postgresql.org) and suddenly
can't login to postgresql as postgres with the normal peer/ident
authentication over a local Unix sock
I have just done an update on my Debian servers running postgresql 9.2
(Postgres is from 9.2.4-2.pgdg70+1 from apt.postgresql.org) and suddenly
can't login to postgresql as postgres with the normal peer/ident
authentication over a local Unix socket.
I've worked around it (I'm using md5 for the ti
