| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jim Nasby <jnasby(at)enova(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Problems with hash join over nested loop |
| Date: | 2013-10-29 14:10:43 |
| Message-ID: | CAHyXU0ydScKt=-5G4yBpHWAh9eO6eV60P6uVCnui+YS9EMY5vw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Mon, Oct 28, 2013 at 6:13 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Jim Nasby <jnasby(at)enova(dot)com> writes:
>> I've been working on trying to normalize a table that's got a bunch of text fields. Normalizing the first 4 has been a non-issue. But when I try and normalize 2 additional fields a bunch of query plans go belly-up.
>
> Try increasing join_collapse_limit/from_collapse_limit. I'm a bit
> confused by your description but I think maybe you've got more than 8
> relations in the subqueries.
Hm -- wondering out loud if there would be any value in terms of
decorating explain output when that limit was hit and if it's
practical to do so...
merlni
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2013-10-29 16:21:26 | Re: Problems with hash join over nested loop |
| Previous Message | Jim Nasby | 2013-10-28 23:53:03 | Re: Problems with hash join over nested loop |