Re: BUG #18348: Inconsistency with EXTRACT([field] from INTERVAL);

From: jian he <jian(dot)universality(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Francisco Olarte <folarte(at)peoplecall(dot)com>, Michael Bondarenko <work(dot)michael(dot)2956(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org, dgrowleyml(at)gmail(dot)com, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
Subject: Re: BUG #18348: Inconsistency with EXTRACT([field] from INTERVAL);
Date: 2024-05-08 01:03:56
Message-ID: CACJufxGFuZsj+31a204fFpxv_RCHA-u1h6WEBZ6qpjBVoio5dQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On Wed, May 8, 2024 at 5:27 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Here's a more fleshed-out patch. I don't think we really need to
> document the behavior for negative intervals; at least, we haven't
> done that so far for any other fields. I did add testing of such
> cases though.
>

the doc looks good to me.
extract quarter from the interval makes sense to me.

but in real life, for week, we generally begin with 1?
like "the first week", "second week"

so should
select extract(week from interval '1 day');
return 1
?

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Chris Travers 2024-05-08 08:02:21 pg_rewind fails on Windows where tablespaces are used
Previous Message Wetmore, Matthew (CTR) 2024-05-07 22:09:34 BUG #18348: Inconsistency with EXTRACT([field] from INTERVAL);

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2024-05-08 01:12:28 Re: bug: copy progress reporting of backends which run multiple COPYs
Previous Message Michael Paquier 2024-05-08 00:45:24 Re: Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~?