> "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
>> "ai" <listar(at)mail(dot)ru> wrote:
>>> Oops.. I just saw, that I send you "correct" (already with "workaround")
>>> sql-code instead of "wrong"...
>>> here is "wrong" (difference is in "SELECT sub3.key3, sub4.value2
>>> FROM" ):
>> OK, that is still happening, and looks wrong to me.
> Yeah, I see it too. It seems to be evaluating the placeholder for the
> COALESCE expression at the wrong join level. Not sure why, yet.
Found it --- the code only fails for the case where the COALESCE
subexpression is referenced in the upper targetlist, but not the quals
(ie, not ON or WHERE). Patch committed, thanks for the report!
regards, tom lane
In response to
pgsql-bugs by date
|Next:||From: Tom Lane||Date: 2011-08-09 05:02:20|
|Subject: Re: BUG #6155: literal definition of arrays with double qoutes leads to error |
|Previous:||From: listar||Date: 2011-08-08 20:22:02|
|Subject: BUG #6155: literal definition of arrays with double qoutes leads to error|