El mié, 11-01-2012 a las 10:40 -0500, Tom Lane escribió:
> Gerardo Herzig writes:
> > Hi all. Im working on a 'simple' query with 7, 8 left joins. After the
> > 9nth join or so, explain analyze became to show the plan with many
> > tables being read in sequential fashion. Of course, this slows dow
Gerardo Herzig writes:
> So, what happens, when a plsql function is excecuted, it takes is own
> enviroment variables, or something like that?
No, but it probably cached a plan from an execution before you changed
join_collapse_limit ...
regards, tom lane
--
Sent via pg
El mié, 11-01-2012 a las 10:40 -0500, Tom Lane escribió:
> Gerardo Herzig writes:
> > Hi all. Im working on a 'simple' query with 7, 8 left joins. After the
> > 9nth join or so, explain analyze became to show the plan with many
> > tables being read in sequential fashion. Of course, this slows dow
Gerardo Herzig writes:
> Hi all. Im working on a 'simple' query with 7, 8 left joins. After the
> 9nth join or so, explain analyze became to show the plan with many
> tables being read in sequential fashion. Of course, this slows down the
> query response in a factor on 10.
increase join_collapse
Hi all. Im working on a 'simple' query with 7, 8 left joins. After the
9nth join or so, explain analyze became to show the plan with many
tables being read in sequential fashion. Of course, this slows down the
query response in a factor on 10.
I can alter the order in wich the join's are appended,
