From: | "ai" <listar(at)mail(dot)ru> |
---|---|
To: | "'Kevin Grittner'" <Kevin(dot)Grittner(at)wicourts(dot)gov>, <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #6154: wrong result with nested left-joins |
Date: | 2011-08-08 14:37:07 |
Message-ID: | 01b401cc55d8$ab9f9140$02deb3c0$@mail.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Kevin, thanks a lot for your answer! As my servers are production systems
and as I have an acceptable workaround for my needs, I will wait around with
a postgresql upgrade =)
I just tried to help with discovering of a potential bug =)) Anyway I'm very
glad to know, that in new version it's not an issue already =)
Kind regards
Alexey Isaiko
Television department consultant
All-Russian Research Institute of TV and Radio Broadcasting
Russian Media Group
TV-channels: RUTV, Hip Hop Hit
-----Original Message-----
From: Kevin Grittner [mailto:Kevin(dot)Grittner(at)wicourts(dot)gov]
Sent: Monday, August 08, 2011 8:52 PM
To: listar; pgsql-bugs(at)postgresql(dot)org
Subject: Re: [BUGS] BUG #6154: wrong result with nested left-joins
"listar" <listar(at)mail(dot)ru> wrote:
> PostgreSQL version: 8.4.5
> Description: wrong result with nested left-joins
> And this is the problem - value2 can't be NULL because of COALESCE in
> sub4 (at least I think that it can't be =))
This works correctly in release 9.0.4 and development HEAD. I don't still
have any machines handy which are running 8.4, but you might want to try it
on the latest bug-fix version of 8.4 (currently
8.4.8) to see if the fix was back-patched.
http://www.postgresql.org/support/versioning
-Kevin
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-08-08 15:01:32 | Re: BUG #6154: wrong result with nested left-joins |
Previous Message | Kevin Grittner | 2011-08-08 13:51:39 | Re: BUG #6154: wrong result with nested left-joins |