Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: greatest/least semantics different between oracle and postgres
- From: Gregory Stark <stark(at)enterprisedb(dot)com>
- To: Bruno Wolff III <bruno(at)wolff(dot)to>
- Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrej Ricnik-Bay <andrej(dot)groups(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
- Subject: Re: greatest/least semantics different between oracle and postgres
- Date: Sat, 30 Jun 2007 16:05:15 +0100
"Bruno Wolff III" <bruno(at)wolff(dot)to> writes: > Also what value should I have used in a coalesce to guaranty still getting > the maximum? I would expect coalesce(coalesce(greatest(a,b),a),b) to do what you want. It's not terribly legible though and if a and b are subselects I would worry a little about the optimizer rerunning them unnecessarily. Perhaps coalesce(greatest(a,b), coalesce(a,b)) is more legible? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com
- Follow-Ups:
- References:
- greatest/least semantics different between oracle and postgres
- From: Bruno Wolff III
- Re: greatest/least semantics different between oracle and postgres
- From: Andrej Ricnik-Bay
- Re: greatest/least semantics different between oracle and postgres
- From: Tom Lane
- Re: greatest/least semantics different between oracle and postgres
- From: Bruno Wolff III
- greatest/least semantics different between oracle and postgres
- Prev by Date: Re: Possible bug (or I don't understand how foreign keys should work with partitions)
- Next by Date: Re: greatest/least semantics different between oracle and postgres
- Previous by thread: Re: greatest/least semantics different between oracle and postgres
- Next by thread: Re: greatest/least semantics different between oracle and postgres
- Indexes: