From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: cwikla@puzzle.io
Subject: BUG #17473: Custom range type with timestamp doesn't respect precision
Date: Fri, 29 Apr 2022 19:19:27 +0000
Message-ID: <17473-0b8caedccc6ee7b1@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 17473
Logged by: John Cwikla
Email address: cwikla@puzzle.io
PostgreSQL version: 14.2
Operating system: Debian 14.2-1.pgdg110+1
Description:
Are range types supposed to respect precision? There is no mention of
precision in the documents that I can find, and it doesn't seem to be the
case for timestamps.
psql (14.2 (Debian 14.2-1.pgdg110+1))
SSL connection (protocol: TLSv1.3, cipher: TLS_AES_256_GCM_SHA384, bits:
256, compression: off)
Type "help" for help.
postgres=> CREATE TYPE tstzrange3 AS RANGE ( subtype = timestamp(3) with
time zone);
CREATE TYPE
postgres=> select tstzrange3(NOW(), NULL);
tstzrange3
------------------------------------
["2022-04-29 19:11:31.920322+00",)
(1 row)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, cwikla@puzzle.io
Subject: Re: BUG #17473: Custom range type with timestamp doesn't respect precision
In-Reply-To: <17473-0b8caedccc6ee7b1@postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox