Re: date_trunc() in a specific time zone

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Paul A Jungwirth <pj(at)illuminatedcomputing(dot)com>
Cc: vik(dot)fearing(at)2ndquadrant(dot)com, Steve Crawford <scrawford(at)pinpointresearch(dot)com>, andreas(at)proxel(dot)se, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: date_trunc() in a specific time zone
Date: 2018-10-29 16:53:16
Message-ID: 8424.1540831996@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Paul A Jungwirth <pj(at)illuminatedcomputing(dot)com> writes:
> It would be nice to support both timestamptz and timestamp, with the
> output matching whatever type you give as input. I know which to use
> is controversial, but plain timestamp is the default in Ruby on Rails,
> so people encounter it a lot.

We already have date_trunc() for timestamp-without-tz, so I'm a little
confused as to what you think is/would be missing.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Paul A Jungwirth 2018-10-29 16:58:58 Re: date_trunc() in a specific time zone
Previous Message Paul A Jungwirth 2018-10-29 16:50:07 Re: date_trunc() in a specific time zone