Received: from maia.hub.org (maia-3.hub.org [200.46.204.243])
	by mail.postgresql.org (Postfix) with ESMTP id 5BEF76329E9
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Mon, 14 Jun 2010 10:59:47 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia,
	port 10024) with ESMTP id 00524-02
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Mon, 14 Jun 2010 13:59:38 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
	by mail.postgresql.org (Postfix) with ESMTP id D1049632350
	for <pgsql-performance@postgresql.org>;
	Mon, 14 Jun 2010 10:59:39 -0300 (ADT)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id o5EDxXT2012073;
	Mon, 14 Jun 2010 09:59:33 -0400 (EDT)
To: Magnus Hagander <magnus@hagander.net>
cc: David Jarvis <thangalin@gmail.com>,
	Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>,
	pgsql-performance <pgsql-performance@postgresql.org>
Subject: Re: Analysis Function 
In-reply-to: <AANLkTik5qoLZUtGnakVXIYUTHZoOTYvLlHqBFY-w2GaB@mail.gmail.com> 
References: <AANLkTikihIMleazgqo1NhLo7LA5Tiujz4TIfBL1agxAp@mail.gmail.com>
	<AANLkTikZKwBCR8QfGph3aH34A2dJ2NQyOjq-Pt3eZ3_z@mail.gmail.com>
	<4C119B3E.3090608@squeakycode.net>
	<AANLkTinjUmGWmB3jsjj-6w_44c0K7f_wSrH_1TALPaOY@mail.gmail.com>
	<m34ohahrp4.fsf@passepartout.tim-landscheidt.de>
	<AANLkTik3l6uedzVJLqn-nueNva46NAFwxbpSe1XSc26_@mail.gmail.com>
	<m3typ9hl6a.fsf@passepartout.tim-landscheidt.de>
	<AANLkTikPcYh1vMxVynxGnD4RCch8-DMixiGK1v9kO17Z@mail.gmail.com>
	<AANLkTim6TrfgLiXM3sTSx6rgXQ3zNLTWBTD_MbU0OPsv@mail.gmail.com>
	<12241.1276287655@sss.pgh.pa.us>
	<AANLkTil8w33uYIadqvvecTEvTmY9aNvstpuiy1tryyT7@mail.gmail.com>
	<AANLkTinPNQZv_9BS1fkoLPXzcBZe8FFv77PBRhPR-GpL@mail.gmail.com>
	<4C14746F.9050603@enterprisedb.com>
	<13998.1276443260@sss.pgh.pa.us>
	<AANLkTinUYpgGbtwYvaf01_-6QW6CTxEjaJmceVZg7_wX@mail.gmail.com>
	<AANLkTik5qoLZUtGnakVXIYUTHZoOTYvLlHqBFY-w2GaB@mail.gmail.com>
Comments: In-reply-to Magnus Hagander <magnus@hagander.net>
	message dated "Mon, 14 Jun 2010 11:03:37 +0200"
Date: Mon, 14 Jun 2010 09:59:33 -0400
Message-ID: <12072.1276523973@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9,
	T_RP_MATCHES_RCVD=-0.01
X-Spam-Level: 
X-Archive-Number: 201006/245
X-Sequence-Number: 39101

Magnus Hagander <magnus@hagander.net> writes:
> On Sun, Jun 13, 2010 at 21:19, David Jarvis <thangalin@gmail.com> wrote:
>> I prefer to_timestamp and to_date over the more verbose construct_timestamp.

> Yeah, I agree with that.

Those names are already taken.  It will cause confusion (of both people
and machines) if you try to overload them with this.

			regards, tom lane