Re: ago(interval) → timestamptz

Поиск
Список
Период
Сортировка
Искать
От
Laurenz Albe
Тема
Re: ago(interval) → timestamptz
Дата
Msg-id
f50f5f0ac21493db560f7f046db6da38bc4336a6.camel@cybertec.at
Ответ на
Список
Дерево обсуждения
ago(interval) → timestamptz Florents Tselai <florents.tselai@gmail.com>
Re: ago(interval) → timestamptz Laurenz Albe <laurenz.albe@cybertec.at>
Re: ago(interval) → timestamptz Andreas Karlsson <andreas@proxel.se>
Re: ago(interval) → timestamptz Florents Tselai <florents.tselai@gmail.com>
Re: ago(interval) → timestamptz Laurenz Albe <laurenz.albe@cybertec.at>
Re: ago(interval) → timestamptz Andreas Karlsson <andreas@proxel.se>
Re: ago(interval) → timestamptz Laurenz Albe <laurenz.albe@cybertec.at>
Re: ago(interval) → timestamptz Quan Zongliang <quanzongliang@yeah.net>
On Thu, 2025-11-06 at 12:15 +0100, Florents Tselai wrote:
> > I don't get what users would need ago(interval) -> timestamp. That function would
> > not make any sense since there is no equivalent to now() which returns timestamp,
> > simply because a timestamp does not refer to any specific point in time and can
> > only be interpreted with some additional piece of information like a time zone.
> 
> I agree that only a timestamptz variant makes sense.

Lots of people model absolute time using "timestamp without time zone" with the
silent assumption that all such timestamps are UTC timestamps.  That would be
the additional piece of information.

But I admit that that makes date arithmetic less useful.

There is an equivalent for "now()": localtimestamp

Yours,
Laurenz Albe


В списке pgsql-hackers по дате отправления
От: Chao Li
Дата:
От: Bryan Green
Дата:
FAQ