| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
| Cc: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: truncating timestamps on arbitrary intervals |
| Date: | 2021-03-27 17:06:11 |
| Message-ID: | 20210327170611.GB15100@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Mar 24, 2021 at 08:50:59PM +0100, Peter Eisentraut wrote:
> On 24.03.21 18:58, John Naylor wrote:
> > > As a potential follow-up, should we perhaps add named arguments? That
> > > might make the invocations easier to read, depending on taste.
> >
> > I think it's quite possible some users will prefer that. All we need is
> > to add something like
> >
> > proargnames => '{bin_width,input,origin}'
> >
> > to the catalog, right?
>
> right, plus some documentation adjustments perhaps
+1
The current docs seem to be missing a "synopsis", like
+<synopsis>
+date_trunc(<replaceable>stride</replaceable>, <replaceable>timestamp</replaceable>, <replaceable>origin</replaceable>)
+</synopsis>
--
Justin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kazutaka Onishi | 2021-03-27 17:37:06 | Re: TRUNCATE on foreign table |
| Previous Message | Tom Lane | 2021-03-27 16:30:07 | Re: making update/delete of inheritance trees scale better |