Re: BRIN minmax multi - incorrect distance for infinite timestamp/date
От | Tomas Vondra |
---|---|
Тема | Re: BRIN minmax multi - incorrect distance for infinite timestamp/date |
Дата | |
Msg-id | 3e21dbbe-3613-6012-ee15-aee3db9674af@enterprisedb.com обсуждение исходный текст |
Ответ на | Re: BRIN minmax multi - incorrect distance for infinite timestamp/date (Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>) |
Ответы |
Re: BRIN minmax multi - incorrect distance for infinite timestamp/date
|
Список | pgsql-hackers |
On 10/20/23 11:52, Ashutosh Bapat wrote: > On Thu, Oct 19, 2023 at 6:11 PM Ashutosh Bapat > <ashutosh.bapat.oss@gmail.com> wrote: >> >> I think we should provide generate_series(date, date, integer) which >> will use date + integer -> date. > > Just to be clear, I don't mean that this patch should add it. > I'm not against adding such generate_series() variant. For this patch I'll use something like the query you proposed, I think. I was thinking about the (date + interval) failure a bit more, and while I think it's confusing it's not quite wrong. The problem is that the interval may have hours/minutes, so it makes sense that the operator returns timestamp. That's not what most operators do, where the data type does not change. So a bit unexpected, but seems correct. regards -- Tomas Vondra EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: