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

Re: BUG #5338: PG_DUMP fails due to invalid adnum value

From: Toni Helenius <Toni(dot)Helenius(at)syncrontech(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #5338: PG_DUMP fails due to invalid adnum value
Date: 2010-02-25 06:58:53
Message-ID: E6A9CAA76548CB4EB02D2E3B174DD3B138ECA0E12B@ink.sad.syncrontech.com (view raw or flat)
Thread:
Lists: pgsql-bugs
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 :/

-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us] 
Sent: 24. helmikuuta 2010 17:55
To: Toni Helenius
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: [BUGS] BUG #5338: PG_DUMP fails due to invalid adnum value 

Toni Helenius <Toni(dot)Helenius(at)syncrontech(dot)com> writes:
> I actually managed to trace this so that I can reproduce the crashing simply with an empty table created as in attachment. If I delete the table, everything is fine. The table can be empty and pg_dump still crashes. This is really weird...

Works for me --- I ran that script and could dump the table no problem.

I'm still thinking this is corruption in your copy of pg_attrdef; maybe
its indexes are messed up.  Try reindexing it.

BTW, you forgot to attach the pg_attrdef query output ...

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Kovács ZoltánDate: 2010-02-25 07:30:19
Subject: Re: BUG #5345: non-administrator users cannot create databases with special encoding
Previous:From: Alex HunsakerDate: 2010-02-25 06:34:18
Subject: Re: New PL/Perl failure with Safe 2.2x due to recursion (8.x & 9.0)

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