From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Sebastien Flaesch <sebastien(dot)flaesch(at)4js(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: SUM() of INTERVAL type produces INTERVAL with no precision |
Date: | 2021-12-03 16:30:08 |
Message-ID: | dc685734-0bf8-fa28-f280-bf3b340e60b6@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 12/3/21 08:12, Sebastien Flaesch wrote:
>
> Hum....
>
> test1=> create table tab2 ( i interval hour to minute );
> CREATE TABLE
> test1=> insert into tab2 values ( interval '9999-10 555 11:22:33' );
> INSERT 0 1
> test1=> select * from tab2;
> i
> --------------------------------------
> 9999 years 10 mons 555 days 11:22:00
> (1 row)
>
> Expected?
>
> Qualifiers "hour to minute" seem just to be some decoration...
https://www.postgresql.org/docs/current/datatype-datetime.html#DATATYPE-INTERVAL-INPUT
"... Also, field values “to the right” of the least significant field
allowed by the fields specification are silently discarded. For example,
writing INTERVAL '1 day 2:03:04' HOUR TO MINUTE results in dropping the
seconds field, but not the day field."
>
> Seb
> ------------------------------------------------------------------------
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Dmitry Dolgov | 2021-12-03 16:31:08 | Re: Max connections reached without max connections reached |
Previous Message | Daniel Frey | 2021-12-03 16:25:23 | Re: libpq: Which functions may hang due to network issues? |