Re: Problems with Greatest

From: Teddy Schmitz <teddy(dot)schmitz(at)actuallywedo(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Problems with Greatest
Date: 2017-02-16 04:45:49
Message-ID: SINPR0101MB16942546A9A0567FF618E34B835A0@SINPR0101MB1694.apcprd01.prod.exchangelabs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Thanks for the link Pavel, that makes perfect sense now.

Teddy

________________________________
From: David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
Sent: Thursday, February 16, 2017 12:42:36 PM
To: Teddy Schmitz
Cc: pgsql-general(at)postgresql(dot)org
Subject: [GENERAL] Problems with Greatest

On Wednesday, February 15, 2017, Teddy Schmitz <teddy(dot)schmitz(at)actuallywedo(dot)com<javascript:_e(%7B%7D,'cvml','teddy(dot)schmitz(at)actuallywedo(dot)com');>> wrote:

select greatest(max(t1.id), max(t2.id)) from t1, t2;

I seriously doubt that the greatest function is a larger contributor to run time than the cross join between t1 and t2.

David J.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Thomas Kellerer 2017-02-16 07:10:25 Re: Problems with Greatest
Previous Message David G. Johnston 2017-02-16 04:42:36 Problems with Greatest