From: Raf <rafiq@joshua.dreamthought.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: Manual trigger removal [WAS] Flushing Postgres Function Cache
Date: Thu, 17 May 2007 14:54:40 +0100 (BST)
Message-ID: <20070517145059.W69332@joshua.dreamthought.com> (raw)
In-Reply-To: <23181.1179409363@sss.pgh.pa.us>
References: <20070517092853.R69332@joshua.dreamthought.com>
<20070517122322.V69332@joshua.dreamthought.com>
<20070517131522.T69332@joshua.dreamthought.com>
<20070517135952.F69332@joshua.dreamthought.com>
<23181.1179409363@sss.pgh.pa.us>
Hi Tom,
Thanks for the feedback.
On Thu, 17 May 2007, Tom Lane wrote:
> 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?
Even though there were 0 rows associated with the table's oid in
pg_depend and pg_triggers ?
Should this not be my indicator of the reltriggers count?
For completeness, I ran a script we have which runs a bunch of alter
tables, so that the schema returns to its natural state. I believe that
this should fix any missing triggers, once the redundant trigger had been
removed. Would you agree?
Thanks,
Raf
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: rafiq@joshua.dreamthought.com, tgl@sss.pgh.pa.us
Subject: Re: Manual trigger removal [WAS] Flushing Postgres Function Cache
In-Reply-To: <20070517145059.W69332@joshua.dreamthought.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