| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | chris <chrisk(at)pgsqlrocket(dot)com> |
| Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: selecting timestamp |
| Date: | 2018-02-27 20:26:27 |
| Message-ID: | CAKFQuwZ3DYbuFwP+HAmEyPcf29adBFHJ5ME4jSOWzeuhnwN5cA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Feb 27, 2018 at 1:16 PM, chris <chrisk(at)pgsqlrocket(dot)com> wrote:
>
> What is the best way of selecting current timestamp in UTC?
>
You
haven't
define
d
criteria upon which to judge - and the list below is not exhaustive
(but sufficiently so)
>
> SELECT
> CURRENT_TIMESTAMP as ct1
>
standard conforming, assumes server configured for UTC
> ,timezone('UTC',CURRENT_TIMESTAMP) as ct2
> ,timezone('utc',now()) as ct3
>
non-standard, personally non-obvious (the function looks like an
implementation detail that should be avoided)
,CURRENT_TIMESTAMP at time zone 'UTC' as ct4
>
This -
standard conforming and doesn't require assumptions about the calling
environment
,NOW() at time zone 'utc' as ct5
>
non-standard but frequently used; no semantic different compared to the
previous entry
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2018-02-27 20:33:46 | Re: selecting timestamp |
| Previous Message | Adrian Klaver | 2018-02-27 20:25:20 | Re: selecting timestamp |