Re: greatest/least semantics different between oracle and postgres - Mailing list pgsql-general

From Tom Lane
Subject Re: greatest/least semantics different between oracle and postgres
Date
Msg-id 25612.1183217690@sss.pgh.pa.us
Whole thread Raw
In response to Re: greatest/least semantics different between oracle and postgres  (Gregory Stark <stark@enterprisedb.com>)
Responses Re: greatest/least semantics different between oracle and postgres  (Gregory Stark <stark@enterprisedb.com>)
List pgsql-general
Gregory Stark <stark@enterprisedb.com> writes:
> "Bruno Wolff III" <bruno@wolff.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.

That does not work correctly for volatile functions, and it does not
scale to more than two inputs either -- you'd get the first nonnull
not the largest one.

            regards, tom lane

pgsql-general by date:

Previous
From: Oleg Bartunov
Date:
Subject: Re: stem & tsearch2, want different stemmed words
Next
From: Tom Lane
Date:
Subject: Re: greatest/least semantics different between oracle and postgres