From: | Paul A Jungwirth <pj(at)illuminatedcomputing(dot)com> |
---|---|
To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
Cc: | Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: range_agg |
Date: | 2019-07-10 04:18:44 |
Message-ID: | CA+renyW9E4eCA0p6n6-LgPDzFmEp2asG0cg2USr8G2hL_iG5og@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Jul 9, 2019 at 12:02 PM Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
> > - Multirange in/out work just like arrays, e.g. '{"[1,3)", "[5,6)"}'
>
> It would be cool to have a better text representation. We could go
> simple like:
>
> '[1,3) [5,6)'
Will that work with all ranges, even user-defined ones? With a
tstzrange[] there is a lot of quoting:
=# select array[tstzrange(now(), now() + interval '1 hour')];
array
---------------------------------------------------------------------------
{"[\"2019-07-09 12:40:20.794054-07\",\"2019-07-09 13:40:20.794054-07\")"}
I'm more inclined to follow the array syntax both because it will be
familiar & consistent to users (no need to remember any differences)
and because it's already built so we can use it and know it won't have
gotchas.
> I think "complement" might be a better name than "inverse".
>
> m1 - m2 = m1 * complement(m2)
>
> What about "~"?
That seems like the right term and a good symbol.
Paul
From | Date | Subject | |
---|---|---|---|
Next Message | Kyotaro Horiguchi | 2019-07-10 04:19:14 | Re: [HACKERS] WAL logging problem in 9.4.3? |
Previous Message | Kyotaro Horiguchi | 2019-07-10 04:18:10 | Re: Remove page-read callback from XLogReaderState. |