Skip site navigation (1) Skip section navigation (2)

Re: dump/restore to 7.4devel giving "[archiver (db)] error returned by PQputline"

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Ron Mayer" <ron(at)intervideo(dot)com>
Cc: "PostgreSQL General" <pgsql-general(at)postgresql(dot)org>
Subject: Re: dump/restore to 7.4devel giving "[archiver (db)] error returned by PQputline"
Date: 2003-04-30 05:24:27
Message-ID: 20003.1051680267@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-general
"Ron Mayer" <ron(at)intervideo(dot)com> writes:
> I can create a one-row-table
>    create table tmp_bad as select * from d_ref where ref_id=145278;
> and dump it
>    copy tmp_bad to '/tmp/zzz';
> and I see the "0x0d" in a hex dump of that file as well.

> Given your first statement, I think this means my old 7.2 database is
> somehow broken.

Hm [sounds of digging in archives] ... it looks like the fix to emit
"\r" rather than an actual 0x0d byte was applied between 7.2 and 7.2.1.
If that's an actual 7.2 installation, I can offer you many excellent
reasons why you should update it to 7.2.4 forthwith ...

> Later, (though probably not til the weekend) I'd be happy to try
> the tcpdump if that's a better tool, though; since it sounds like
> the new protocol should have recovered more gracefully than it did.

Yes, there's still the question of why it lost sync after the first
error.  Please investigate when you get a chance.

			regards, tom lane


In response to

Responses

pgsql-general by date

Next:From: Jim C. NasbyDate: 2003-04-30 05:56:11
Subject: Re: Optimizer not using index on 120M row table
Previous:From: Ron MayerDate: 2003-04-30 05:03:17
Subject: Re: dump/restore to 7.4devel giving "[archiver (db)] error returned by PQputline"

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group