X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 845EC9FB33B for ; Fri, 14 Jul 2006 17:34:00 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 61802-04 for ; Fri, 14 Jul 2006 17:33:56 -0300 (ADT) X-Greylist: delayed 00:15:01.578754 by SQLgrey- Received: from exchange.musicreports.com (unknown [207.47.100.34]) by postgresql.org (Postfix) with ESMTP id AFFFE9FB334 for ; Fri, 14 Jul 2006 17:33:56 -0300 (ADT) Received: from [192.168.20.39] (RG-XP [192.168.20.39]) by exchange.musicreports.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id MB1PWDPV; Fri, 14 Jul 2006 13:18:53 -0700 Message-ID: <44B7FCA1.40006@musicreports.com> Date: Fri, 14 Jul 2006 13:20:49 -0700 From: Roger Ging User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Broken pg_class table Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200607/132 X-Sequence-Number: 22378 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?