From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | John McCawley <nospam(at)hardgeus(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Possible outer join bug with coalesce in 8.2 |
Date: | 2007-02-15 04:37:11 |
Message-ID: | 15696.1171514231@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
John McCawley <nospam(at)hardgeus(dot)com> writes:
> My development machine is PostgreSQL 8.1.5, and my production machine is
> PostgreSQL 8.2. Until now I haven't run into any differences in
> behavior. I have a query with a relatively wacky join, and while it was
> working on my development machine, it wouldn't work on the production
> machine. The query is as follows:
Is this 8.2.0? Because the query seems to match the conditions for this
8.2.1 bug fix:
2006-12-07 14:33 tgl
* src/backend/optimizer/plan/: initsplan.c (REL8_2_STABLE),
initsplan.c: Repair incorrect placement of WHERE clauses when there
are multiple, rearrangeable outer joins and the WHERE clause is
non-strict and mentions only nullable-side relations. New bug in
8.2, caused by new logic to allow rearranging outer joins. Per bug
#2807 from Ross Cohen; thanks to Jeff Davis for producing a usable
test case.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | A. Kretschmer | 2007-02-15 06:00:45 | Re: Cast record as text |
Previous Message | marcelo Cortez | 2007-02-15 04:18:25 | Re: PGSQL 8.2.3 Installation problem |