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

Re: BUG #1542: pg_dump seg fault

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Andrew Slobodyanyk" <slob(at)ukr(dot)net>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #1542: pg_dump seg fault
Date: 2005-03-14 18:39:59
Message-ID: 21023.1110825599@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
"Andrew Slobodyanyk" <slob(at)ukr(dot)net> writes:
> Description:        pg_dump seg fault

> After power failure any operation with tbl_test return "ERROR: could not
> open relation 1663/17242/40429: No such file or directory". I try to get
> information from other tables, but with or without (after deleting that
> table) pg_dump crashes with seg. fault. Backtrace is:
> pg_dump: reading rewrite rules

> Program received signal SIGSEGV, Segmentation fault.
> getRules (numRules=0x0) at pg_dump.c:3159
> 3159                    ruleinfo[i].dobj.namespace =
> ruleinfo[i].ruletable->dobj.namespace;

Hmmm.  What did you do to "delete that table" exactly?  The crash
suggests that there is a row in pg_rewrite that links to a nonexistent
row in pg_class.  It'd be better if pg_dump emitted a more useful
failure message, of course, but the real question is how did your
system catalogs get into such a state ...

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Richard NeillDate: 2005-03-14 23:18:27
Subject: Re: BUG #1540: Enhancement request: 'ambiguous' column reference
Previous:From: Greg StarkDate: 2005-03-14 16:51:18
Subject: Re: [BUGS] We are not following the spec for HAVING without GROUP

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