From: Tom Lane <tgl@sss.pgh.pa.us>
To: Raf <rafiq@joshua.dreamthought.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Manual trigger removal [WAS] Flushing Postgres Function Cache
Date: Thu, 17 May 2007 09:42:43 -0400
Message-ID: <23181.1179409363@sss.pgh.pa.us> (raw)
In-Reply-To: <20070517135952.F69332@joshua.dreamthought.com>
References: <20070517092853.R69332@joshua.dreamthought.com>
<20070517122322.V69332@joshua.dreamthought.com>
<20070517131522.T69332@joshua.dreamthought.com>
<20070517135952.F69332@joshua.dreamthought.com>
Raf <rafiq@joshua.dreamthought.com> writes:
> The final step was the decrement the reltriggers counter for the parent
> table's pg_class entry to 0. This appears to have resolved the problem.
You should probably have set it to 3 not 0; what you did has disabled
*all* the triggers on that table. Is that really what you want?
> I'm curious as to whether the problem may have resulted from slony
> corruptting internal pg_<tables> or postgres not correctly respecting the
> integrity of drop-trigger type transactions and their respective
> dependencies.
You'd be better off asking about that on the Slony mailing lists.
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, rafiq@joshua.dreamthought.com
Subject: Re: Manual trigger removal [WAS] Flushing Postgres Function Cache
In-Reply-To: <23181.1179409363@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