Re: BUG #4945: Parallel update(s) gone wild - Mailing list pgsql-bugs

From Craig Ringer
Subject Re: BUG #4945: Parallel update(s) gone wild
Date
Msg-id 1248755018.10632.180.camel@wallace.localnet
Whole thread Raw
In response to BUG #4945: Parallel update(s) gone wild  ("dan boeriu" <dan.boeriu@roost.com>)
List pgsql-bugs
On Mon, 2009-07-27 at 21:56 +0000, dan boeriu wrote:

> What I noticed is that the second will not finish if the READ table has many
> rows to be read (1 million let's say) but it finishes when the read table
> has only a few 1000s of rows.
> Any idea why?

It could be that it _does_ finish ... eventually. It might be doing
something that scales very poorly with number of input rows, like a
nested loop within a nested loop.

Can you provide EXPLAIN ANALYZE output for the problem query?

--
Craig Ringer

pgsql-bugs by date:

Previous
From: "Fabiano"
Date:
Subject: BUG #4946: bug - libiconv-2.dll
Next
From: Craig Ringer
Date:
Subject: Re: BUG #4945: Parallel update(s) gone wild