From: Roger Ging <roger@musicreports.com>
To: pgsql-admin@postgresql.org
Subject: Broken pg_class table
Date: Fri, 14 Jul 2006 13:20:49 -0700
Message-ID: <44B7FCA1.40006@musicreports.com> (raw)
I accidentally wrecked the pg_class table in a database by leaving off
the where clause of an update statement when setting the reltriggers
back to the count from pg_trigger after a bulk data load. I can no
longer connect to the database, although it does start up without
error. running psql [dbname] causes extreme cpu load, and the command
just hangs. Memory usage continues climbing until a oom killer crashes
everything. I presume that my blunder is causing some sort of infinite
loop during postmaster startup for the spawned process. Is there a way
I can get direct access to the file for pg_class and reset the
reltriggers to the correct values without a full dbinit process?
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: roger@musicreports.com
Subject: Re: Broken pg_class table
In-Reply-To: <44B7FCA1.40006@musicreports.com>
References: <44B7FCA1.40006@musicreports.com>
* 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