Re: ago(interval) → timestamptz

Поиск
Список
Период
Сортировка
Искать
От
Laurenz Albe
Тема
Re: ago(interval) → timestamptz
Дата
Msg-id
8bf621c358b84f62e2f51f0ab2fb0758da722e49.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 Mon, 2025-11-03 at 22:36 +0100, Florents Tselai wrote:
> I realize this will get some "you can easily implement this yourself” pushback,
> But I keep seeing and writing a lot of WHERE ts > now() - interval '1 day' expressions.

You can easily implement this yourself...
Also, there already is something similar in the shape of 'yesterday'::timestamptz.
Moreover, a good percentage of the users would instead need ago(interval) -> timestamp.

So I'd say that the added value is marginal, and I personally find

   current_timestamp - INTERVAL '1' DAY

more readable and more SQL standard compliant than

   ago('1 day')

Yours,
Laurenz Albe


В списке pgsql-hackers по дате отправления
От: Michael Paquier
Дата:
От: jian he
Дата:
FAQ