Re: BUG #5414: pg_dump failure from database 8.4.3 to 8.4.3

From: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
To: "y(dot)y(dot)chen" <yychen(at)clhs(dot)tyc(dot)edu(dot)tw>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5414: pg_dump failure from database 8.4.3 to 8.4.3
Date: 2010-04-13 08:13:12
Message-ID: 4BC42798.7040008@postnewspapers.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 13/04/10 09:03, y.y.chen wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5414
> Logged by: y.y.chen
> Email address: yychen(at)clhs(dot)tyc(dot)edu(dot)tw
> PostgreSQL version: 8.4.3
> Operating system: XP and openSuSE 11.1
> Description: pg_dump failure from database 8.4.3 to 8.4.3
> Details:
>
> pg_dump execute failure at dump from host to other host down in all OS!
>
> pg_dump from 8.4.2 to 8.4.3 is OK!
> But pg_dump from 8.4.3 to 8.4.3 alway be failure!
> My SQL struction is
> "pg_dump -h192.168.0.17 -O db |psql -p5432 db"
>
> It can not do finished , It will be down !

Error message?

Does this happen with a blank database, or just with your `db' ?

If you pg_dump to a file instead of piping to psql, does that work?

If you then restore that file using psql, does that work?

--
Craig Ringer

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Magnus Hagander 2010-04-13 08:16:25 Re: Possible alpha5 SR bug
Previous Message Kenaniah Cerny 2010-04-13 08:03:45 BUG #5417: intarray adds <@ operator which breaks infromation_schema.referential_constraints