Re: BUG #5338: PG_DUMP fails due to invalid adnum value - Mailing list pgsql-bugs

From Robert Haas
Subject Re: BUG #5338: PG_DUMP fails due to invalid adnum value
Date
Msg-id 603c8f071002251147j42ab6f01j52895e6b3c47e646@mail.gmail.com
Whole thread Raw
In response to Re: BUG #5338: PG_DUMP fails due to invalid adnum value  (Toni Helenius <Toni.Helenius@syncrontech.com>)
List pgsql-bugs
On Thu, Feb 25, 2010 at 1:58 AM, Toni Helenius
<Toni.Helenius@syncrontech.com> wrote:
> I reindexed everything and vacuumed. The system tables and our tables. It didn't work. I get the following:
>
>
> pg_dump: finding the columns and types of table "bsc_day1_001"
> pg_dump: finding default expressions of table "bsc_day1_001"
>
> Prosessi palautti lopetuskoodin -1073741819 | (lopetuskoodin = exit code)
>
> With:
> C:\Program Files (x86)\PostgreSQL\8.3\bin\pg_dump.exe -h localhost -p 5432 -U postgres -F c -b -v -f
"D:\SyncronTech\Asennus\Migraatio\vkotos.backup"vkotos 
>
> Could this be 64-bit Windows 2008 SP1 issue? Or Xeon CPU? I don't know, sounds bit weird :/

It's almost got to be a data corruption issue, but you still haven't
supplied the output of the query Tom suggested in his first response.

...Robert

pgsql-bugs by date:

Previous
From: "David E. Wheeler"
Date:
Subject: Re: New PL/Perl failure with Safe 2.2x due to recursion (8.x & 9.0)
Next
From: Robert Haas
Date:
Subject: Re: BUG #5314: Error in nested composite types in plpgsql.