daterange() is ignoring 3rd boundaries argument

From: Robert KOFLER <rk(at)marksim(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: daterange() is ignoring 3rd boundaries argument
Date: 2022-11-28 23:50:51
Message-ID: adb48d1b-0993-0921-9f08-c34ba8333a39@marksim.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

select daterange('2022-11-01'::date, '2023-01-31'::date, '()')
returns
[2022-11-02,2023-01-31) which is deafult of [)
instead of
(2022-11-02,2023-01-31)

Version
PostgreSQL 14.6 (Ubuntu 14.6-1.pgdg20.04+1) on x86_64-pc-linux-gnu,
compiled by gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0, 64-bit

from manual: 8.17.6. Constructing Ranges and Multiranges

Each range type has a constructor function with the same name as the
range type. Using the constructor function is frequently more convenient
than writing a range literal constant, since it avoids the need for
extra quoting of the bound values. The constructor function accepts two
or three arguments. The two-argument form constructs a range in standard
form (lower bound inclusive, upper bound exclusive), while the
three-argument form constructs a range with bounds of the form specified
by the third argument.


with best regards
Mag. Robert Kofler / Managing Partner

MARKSIM SERVICES GMBH
A-1220 Vienna / Austria, Oberdorfstrasse 9/1/15
https://statshop.marksim.net
rk(at)marksim(dot)net

MARKSIM^® Conjoint And Market Simulation — We Simulate Future Market
Success

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Richard Guo 2022-11-29 00:12:16 Re: BUG #17700: An assert failed in prepjointree.c
Previous Message Andres Freund 2022-11-28 21:16:39 Re: BUG #17693: Slow performance: Much slower queries on pg_stat_all_tables since 13.4