From: | Edmund Bacon <ebacon(at)onesystem(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Spurious rows returned with left join? |
Date: | 2006-04-04 21:58:06 |
Message-ID: | 4432EBEE.20006@onesystem.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom Lane wrote:
>Edmund Bacon <ebacon(at)onesystem(dot)com> writes:
>
>
>>Consider the following:
>>...
>>Note that I get 2 rows where t1_a = 3.
>>
>>
>
>Are you getting a Merge Right Join plan for that? If so, you're likely
>getting bit by this bug:
>
>2006-03-17 14:38 tgl
>
>
>
That's correct. After doing an analyze on t1,t2,t3 the plan changed to
Hash Left Join, and I got the expected results.
>This'll be fixed in 8.1.4, or if you're in a hurry you can get the patch
>from our CVS server.
>
> regards, tom lane
>
>
No great worries. As remarked in original post, by doing the inner join
first, I got the right results. I didn't see anything in the archives
about this, so I thought it might be an unknown issue. Admittedly, I
didn't scour the archives too thouroghly ..
Edmund
From | Date | Subject | |
---|---|---|---|
Next Message | patrick | 2006-04-04 22:52:10 | Re: recover from base directory? |
Previous Message | Tom Lane | 2006-04-04 21:53:01 | Re: CREATE TABLE (with INHERITS) and ACCESS EXCLUSIVE locks |