| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Oliver Elphick <olly(at)lfix(dot)co(dot)uk> |
| Cc: | Martijn van Oosterhout <kleptog(at)svana(dot)org>, pgsql-general(at)postgresql(dot)org, "Bhavana(dot)Rakesh" <Bhavana(dot)Rakesh(at)noaa(dot)gov> |
| Subject: | Re: jdbc pg_hba.conf error |
| Date: | 2007-05-30 17:28:18 |
| Message-ID: | 5646.1180546098@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Oliver Elphick <olly(at)lfix(dot)co(dot)uk> writes:
> His original message (which I snipped) said he had:
> # IPv4-style local connections:
> host all all 127.0.0.1 255.255.255.255 trust
> host testing123 brakesh 127.0.0.1 255.255.255.255 trust
> So it seems to me he did have it configured.
I've seen similar problems resolved by discovering that (1) the DBA
was editing the wrong copy of the pg_hba.conf file, or (2) there was
actually more than one postmaster running on the machine.
Check "ps" for multiple postmasters. Put a deliberate error in the
pg_hba.conf file and verify that the postmaster fails to restart.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | gonzales | 2007-05-30 17:29:49 | Re: jdbc pg_hba.conf error |
| Previous Message | Bhavana.Rakesh | 2007-05-30 17:21:02 | Re: jdbc pg_hba.conf error |