From: | Dave Page <dpage(at)postgresql(dot)org> |
---|---|
To: | Patrick Headley <linxconsulting(at)comcast(dot)net> |
Cc: | pgadmin-support(at)postgresql(dot)org |
Subject: | Re: PGAdmin III v1.6.1 bug |
Date: | 2006-12-05 09:36:13 |
Message-ID: | 45753D8D.2040408@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Patrick Headley wrote:
> PGAdmin III v1.6.1 binary install
>
> Windows XP SP2 with all known patches
>
>
>
> This was an issue in v1.4.2, as well.
>
>
>
> I can backup a PostgreSQL v8.0.4 database with large objects with no
> problems. However, if I use PGAdminIII v1.6.1 to restore the database I
> receive an error message when pg_restore tries to restore the large
> objects and then the return code is set to 1. I have created a
> pgpass.conf file in the Application Data folder of the profile that I’m
> logged into when using PGAdminIII but that has no effect. If it’s
> supposed to then maybe I did something wrong. The way I successfully
> restore the database is to go into a command window on a different
> machine (Windows Server 2003 in this case) and run pg_restore from
> there. At the point where PGAdminIII fails, the command prompt version
> of pg_restore prompts for the password again.
I cannot reproduce this here. What does your pg_hba.conf entry look like
for the connection from your workstation? Can you provide a simple test
case?
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2006-12-05 09:45:35 | Re: Crash closing loading table edit window |
Previous Message | Dave Page | 2006-12-05 09:29:14 | Re: Inconsistent editing behavior. |