Re: truncating timestamps on arbitrary intervals

Поиск
Список
Период
Сортировка
От John Naylor
Тема Re: truncating timestamps on arbitrary intervals
Дата
Msg-id CAFBsxsEEm1nuhZmfVQxvu_i3nDDEuvNJ_WMrDo9whFD_jusp-A@mail.gmail.com
обсуждение исходный текст
Ответ на Re: truncating timestamps on arbitrary intervals  (John Naylor <john.naylor@2ndquadrant.com>)
Ответы Re: truncating timestamps on arbitrary intervals  (Salek Talangi <salek.talangi@googlemail.com>)
Re: truncating timestamps on arbitrary intervals  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Список pgsql-hackers
On Sat, Mar 27, 2021 at 1:06 PM Justin Pryzby <pryzby@telsasoft.com> wrote:
>
> The current docs seem to be missing a "synopsis", like
>
> +<synopsis>
> +date_trunc(<replaceable>stride</replaceable>, <replaceable>timestamp</replaceable>, <replaceable>origin</replaceable>)
> +</synopsis>

The attached 
- adds a synopsis 
- adds a bit more description to the parameters similar to those in date_trunc
- documents that negative intervals are treated the same as positive ones

Note on the last point: This just falls out of the math, so was not deliberate, but it seems fine to me. We could ban negative intervals, but that would possibly just inconvenience some people unnecessarily. We could also treat negative strides differently somehow, but I don't immediately see a useful and/or intuitive change in behavior to come of that.

--
John Naylor
EDB: http://www.enterprisedb.com
Вложения

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Zhihong Yu
Дата:
Сообщение: Re: Hybrid Hash/Nested Loop joins and caching results from subplans
Следующее
От: Stephen Frost
Дата:
Сообщение: Re: Autovacuum worker doesn't immediately exit on postmaster death