From: Tom Lane <tgl@sss.pgh.pa.us>
To: Colin E. Freas <cef6@georgetown.edu>
Cc: pgsql-admin@postgresql.org
Subject: Re: How to recover when can't start database
Date: Fri, 10 Jun 2005 12:34:15 -0400
Message-ID: <23357.1118421255@sss.pgh.pa.us> (raw)
In-Reply-To: <42A9B2B9.80907@georgetown.edu>
References: <42A9B2B9.80907@georgetown.edu>
"Colin E. Freas" <cef6@georgetown.edu> writes:
> 2005-06-07 16:02:38 EDTLOG: statement: update pg_class set
> reltriggers=foo.c from (select relname,count(tgrelid) as c from
> pg_class,pg_trigger where pg_class.oid=tgrelid and relnamespace=2200
> group by relname) foo;
I'm afraid that database is toast :-(. You managed to overwrite
reltriggers in every row of pg_class, including all the system
catalogs, including some that absolutely positively cannot have
triggers ... like pg_trigger for instance.
-> try to open pg_class
... hmm, it says it has triggers
-> try to open pg_trigger to read triggers
... hmm, it says it has triggers
-> try to open pg_trigger to read triggers
... hmm, it says it has triggers
-> try to open pg_trigger to read triggers
... recurse until out of stack space.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, cef6@georgetown.edu
Subject: Re: How to recover when can't start database
In-Reply-To: <23357.1118421255@sss.pgh.pa.us>
References: <42A9B2B9.80907@georgetown.edu> <23357.1118421255@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox