Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: BUG #3588: coalesce not working in join
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: "Richard Harris" <richard_haris(at)adp(dot)com>
- Cc: pgsql-bugs(at)postgresql(dot)org
- Subject: Re: BUG #3588: coalesce not working in join
- Date: Wed, 29 Aug 2007 20:00:01 -0400
"Richard Harris" <richard_haris(at)adp(dot)com> writes: > Is PG 8.2.4 behavior correct? Nope :-( ... looks like some sorta bug in the rules for when outer joins can be rearranged. It's doing the t1a/t1b join first, and then taking that as the right side of the join to t2, which means that the t1b column goes to null if there's not a match to t2.pkt2. Needs some study ... regards, tom lane
- References:
- BUG #3588: coalesce not working in join
- From: Richard Harris
- BUG #3588: coalesce not working in join
- Prev by Date: Re: BUG #3587: EXECUTE and trigger problem [VASCL:A163D284A86]
- Next by Date: BUG #3589: /etc/init.d/postgresql reload doesn't reflect /etc/postgresql/postgresql.conf log_statement
- Previous by thread: BUG #3588: coalesce not working in join
- Next by thread: Re: BUG #3588: coalesce not working in join
- Indexes: