| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Joel Jacobson <joel(at)compiler(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org, Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>, Isaac Morland <isaac(dot)morland(at)gmail(dot)com> |
| Subject: | Re: [PATCH] Support empty ranges with bounds information |
| Date: | 2021-03-04 07:05:13 |
| Message-ID: | 8793a103a05e4769a10233e2dc1348a4c920c8f1.camel@j-davis.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 2021-03-02 at 18:52 +0100, Joel Jacobson wrote:
> and the theory is only cute until you face the ugly reality.
There are a lot of range functions and operators, as well as different
kinds of ranges (continuous and discrete), and multiranges too. That
means a lot of ways to combine operations in novel ways, and (if we
aren't careful) a lot of ways to produce very unexpected results.
The benefit of falling back on theory is that there's an answer ready
when we need to define or explain the semantics. It might not match
everyone's intuition, but usually avoids the worst kinds of surprises.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiro Ikeda | 2021-03-04 07:14:42 | Re: About to add WAL write/fsync statistics to pg_stat_wal view |
| Previous Message | Michael Paquier | 2021-03-04 07:05:10 | Re: Shared memory size computation oversight? |