"Philippe Lang" <philippe.lang@xxxxxxxxxxxxxx> 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
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
