Skip site navigation (1) Skip section navigation (2)

Re: Manual trigger removal [WAS] Flushing Postgres Function Cache

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Raf <rafiq(at)joshua(dot)dreamthought(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Manual trigger removal [WAS] Flushing Postgres Function Cache
Date: 2007-05-17 13:42:43
Message-ID: 23181.1179409363@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-admin
Raf <rafiq(at)joshua(dot)dreamthought(dot)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

In response to

Responses

pgsql-admin by date

Next:From: RafDate: 2007-05-17 13:54:40
Subject: Re: Manual trigger removal [WAS] Flushing Postgres Function Cache
Previous:From: Johann SpiesDate: 2007-05-17 13:20:33
Subject: Re: ERROR: invalid memory alloc request size

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group