From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
---|---|
To: | Anssi Kääriäinen <anssi(dot)kaariainen(at)thl(dot)fi> |
Cc: | "pgadmin-support(at)postgresql(dot)org" <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: Crash: backup / restore |
Date: | 2010-10-25 15:04:00 |
Message-ID: | 4CC59C60.50206@lelarge.info |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Le 25/10/2010 00:43, Anssi Kääriäinen a écrit :
> On 10/22/2010 02:06 AM, Guillaume Lelarge wrote:
>> The only reason I could guess is that localhost is resolved differently,
>> once in IPv4 and once in IPv6. And that either your pg_hba.conf accepts
>> IPv4 and IPv6 connections but with a different authentication methode,
>> or your .pgpass already has the password for IPv4, and not IPv6 (or
>> vice-versa). Not sure I explained myself clearly :)
>>
>> I think you should check your .pgpass file and your pg_hba.conf file.
>> And be careful about IPv4 and IPv6 resolution.
>>
> Yes, this is it:
> I had this leftover line in pg_hba.conf:
> host all all ::1/128 md5
>
> Removing the line gives me:
> FATAL: no pg_hba.conf entry for host "::1", user "akaariai", ...
>
> And changing md5 to trust fixes the issue.
>
> I wonder if it would be possible to supply -w to pg_dump to make pg_dump
> fail automatically instead of asking for password and thus hanging the
> whole pgadmin program. Unfortunately supported only from version 8.4...
>
This is actually a great idea. I'll try to add this for next release.
You're right that it's only supported from 8.4, but I still think this
is something we should do.
--
Guillaume
http://www.postgresql.fr
http://dalibo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Marie-Claude QUIDOZ | 2010-10-25 16:54:33 | problem with copy from on a windows system |
Previous Message | Anssi Kääriäinen | 2010-10-25 07:43:43 | Re: Crash: backup / restore |