Re: pg_dumpall dies

Den Fri, 20 Feb 2004 23:55:33 -0500. skrev Tom Lane:

> It sounds like you have a badly corrupted database :-(. However, the
> pg_dump message is of little help in delving further than that. What
> shows up in the postmaster log? If the backend is dumping core, can
> you get a stack trace?

The followering is from the log:

2004-02-21 12:52:49 DEBUG: query: SELECT definition, (select usename from pg_user where pg_class.relowner = usesysid) AS viewowner, pg_rewrite.oid, pg_rewrite.rulename FROM pg_rewrite, pg_class, pg_rules WHERE pg_class.relname = 'counter' AND pg_rewrite.ev_class = pg_class.oid AND pg_rules.tablename = pg_class.relname AND pg_rules.rulename = pg_rewrite.rulename ORDER BY pg_rewrite.oid
Server process (pid 24536) exited with status 138 at Sat Feb 21 12:52:49 2004
Terminating any active server processes...
2004-02-21 12:52:49 NOTICE: Message from PostgreSQL backend:
The Postmaster has informed me that some other backend died abnormally and possibly corrupted shared memory.
I have rolled back the current transaction and am going to terminate your database system connection and exit.
Please reconnect to the database system and repeat your query.

The notice is repeated 8 times.

I have set "ulimit -c coredumpsize", but I don't get a core dump.

--
Mvh. / Kind regards
Henrik Farre

http://www.rockhopper.dk