-- Weitergeleitete Nachricht --
Subject: Re: [BUGS] Endless loop in ExecNestLoop
Date: Dienstag, 31. Januar 2006 16:39
From: Tom Lane <[EMAIL PROTECTED]>
To: Philipp Reisner <[EMAIL PROTECTED]>
Cc: pgsql-bugs@postgresql.org
Philipp Reisner <[EMAIL PROTECTED]&
Philipp Reisner <[EMAIL PROTECTED]> writes:
> Well after more research it turned out that sometimes we have a plan
> that executes in less than 2 seconds, and somethimes we get a plan
> does not terminate within 1h30 of CPU time.
Could you send EXPLAIN ANALYZE output for this (at least for the f
Hi,
On Monday 30 January 2006 17:42, Tom Lane wrote:
> > Version: 8.0.2
> I don't think so ... neither bitmap scans nor slot_getattr exist in 8.0.
oops. it is 8.1.2 ..
> Not a lot. You need to find out what the difference is between the
> cases where the query runs quickly and those where it do
> > The explain analyze output shows two levels of hash join underneath
> > four levels of nestloop join, whereas the stack trace looks like there
> > are five levels of nestloop and only one hash. So this is some evidence
> > that a different plan is being used in the slow cases. The stack trac
Am Montag, 30. Januar 2006 17:42 schrieb Tom Lane:
> Philipp Reisner <[EMAIL PROTECTED]> writes:
> > Version: 8.0.2
>
> I don't think so ... neither bitmap scans nor slot_getattr exist in 8.0.
>
Sorry, a typo, 8.1.2 of course.
> > Is this bug-report of any use so far ?
>
> Not a lot. You need to
Philipp Reisner <[EMAIL PROTECTED]> writes:
> Version: 8.0.2
I don't think so ... neither bitmap scans nor slot_getattr exist in 8.0.
> Is this bug-report of any use so far ?
Not a lot. You need to find out what the difference is between the
cases where the query runs quickly and those where it
