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:t...@sss.pgh.pa.us] Sent: 24. helmikuuta 2010 17:55 To: Toni Helenius Cc: pgsql-bugs@postgresql.org Subject: Re: [BUGS] BUG #5338: PG_DUMP fails due to invalid adnum value Toni Helenius <toni.helen...@syncrontech.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 -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
