| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Vinicius Carvalho" <java(dot)vinicius(at)gmail(dot)com> |
| Cc: | pgsql-novice(at)postgresql(dot)org |
| Subject: | Re: Cannot connect though socket |
| Date: | 2006-08-07 03:44:55 |
| Message-ID: | 9274.1154922295@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
"Vinicius Carvalho" <java(dot)vinicius(at)gmail(dot)com> writes:
> Well, here's my pg_hba.conf
> # IPv4 local connections:
> host all all 0.0.0.0 0.0.0.0 password
> host all all 127.0.0.1/32 trust
In that configuration, the second line is a no-op, because the first one
will soak up every incoming IPv4 connection and force it to do password
authentication. pg_hba.conf lines are order-sensitive --- the usual
rule is to put the more restrictive pattern first.
> Both java and pgadmin interfaces complain about: Postgres: FATAL:
> password authentication failed for user "vinicius"
Either you didn't create a database user named "vinicius", or you didn't
give it a password, or you're supplying the wrong password from the
client side ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dylan Fogarty-MacDonald | 2006-08-07 03:59:38 | Scheduling data input from tab delimited file via php |
| Previous Message | Richard Broersma Jr | 2006-08-07 03:13:56 | Re: Cannot connect though socket |