From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | fabriziomello(at)gmail(dot)com, Martijn van Oosterhout <kleptog(at)svana(dot)org>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: patch: make_timestamp function |
Date: | 2013-12-13 20:01:44 |
Message-ID: | 52AB67A8.3070306@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 12/13/2013 02:35 PM, Tom Lane wrote:
> =?ISO-8859-1?Q?Fabr=EDzio_de_Royes_Mello?= <fabriziomello(at)gmail(dot)com> writes:
>> I think the goal of the "make_date/time/timestamp" function series is build
>> a date/time/timestamp from scratch, so the use of 'make_timestamptz' is to
>> build a specific timestamp with timezone and don't convert it.
> Yeah; we don't really want to incur an extra timezone rotation just to get
> to a timestamptz. However, it's not clear to me if make_timestamptz()
> needs to have an explicit zone parameter or not. It could just assume
> that you meant the active timezone.
>
>
Why not overload the function, with one version having the explicit TZ
param?
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Nasby | 2013-12-13 20:04:11 | Re: patch: make_timestamp function |
Previous Message | Fabrízio de Royes Mello | 2013-12-13 19:49:48 | Re: patch: make_timestamp function |