From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alex Burkoff <alex(dot)burkoff(at)jivesoftware(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: execution plan is wrong, or the query ? |
Date: | 2012-12-11 02:09:19 |
Message-ID: | 1858.1355191759@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Alex Burkoff <alex(dot)burkoff(at)jivesoftware(dot)com> writes:
> I have a following query that used to work as intended on 8.3.5 :
> ...
> After upgrade to 9.2 the query doesn't return the same results any more, and the execution plan has changed :
You'd need to provide a self-contained test case if you want an informed
opinion on this. The odds that 8.3.5 was wrong and the newer result is
right are not negligible. (If you were comparing to a *current* 8.3
release I might be more prepared to assume that 9.2 is the one that is
broken.)
FWIW, it looks like the 9.2 plan has been simplified by outer-join
elimination, which implies that unique constraints on the join columns
matter. Possibly you've found a bug in that optimization, but without
a concrete test case it's impossible to be sure, let alone fix it.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Ondrej Ivanič | 2012-12-11 06:40:32 | Re: large database |
Previous Message | Ondrej Ivanič | 2012-12-11 02:02:41 | Re: Problem with aborting entire transactions on error |