From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
Cc: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com>, Aleksander Alekseev <aleksander(at)timescale(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: mark the timestamptz variant of date_bin() as stable |
Date: | 2021-09-01 19:15:42 |
Message-ID: | 2116754.1630523742@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Justin Pryzby <pryzby(at)telsasoft(dot)com> writes:
> On Wed, Sep 01, 2021 at 01:26:26PM -0400, John Naylor wrote:
>> I'm not quite willing to bet the answer couldn't change if the timezone
>> changes, but it's possible I'm the one missing something.
> ts=# SET timezone='-12';
> ts=# SELECT date_bin('1hour', '2021-07-01 -1200', '2021-01-01');
> date_bin | 2021-07-01 00:00:00-12
> ts=# SET timezone='+12';
> ts=# SELECT date_bin('1hour', '2021-07-01 -1200', '2021-01-01');
> date_bin | 2021-07-02 00:00:00+12
Yeah, but those are the same timestamptz value.
Another problem with this example as written is that the origin
values being used are not the same in the two cases ... so I
think it's a bit accidental that the answers come out the same.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | John Naylor | 2021-09-01 19:18:54 | Re: mark the timestamptz variant of date_bin() as stable |
Previous Message | Justin Pryzby | 2021-09-01 18:50:45 | Re: mark the timestamptz variant of date_bin() as stable |