Re: Trigger disactivation and SELECT WAITING

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Philippe Lang" <philippe(dot)lang(at)attiksystem(dot)ch>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Trigger disactivation and SELECT WAITING
Date: 2005-07-26 13:14:22
Message-ID: 26888.1122383662@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Philippe Lang" <philippe(dot)lang(at)attiksystem(dot)ch> writes:
> I have a database with views that can take up to 2 hours to be
> calculated.

> During that time, it's not possible to run a function that inserts data
> into the database, apparently because this function disactivates a
> trigger while it runs, by deleting and creating the trigger again at the
> end. (At least in 7.4.X database, this is the only solution, right?)

"Only solution" to what? Why in the world would a view fool around with
removing triggers?

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2005-07-26 13:26:07 Re: Error when entering template1
Previous Message Filip Wuytack 2005-07-26 11:35:39 Hardware suggestions for a new data warehouse Postgresql/Bizgres server? (6000)