Re: unnesting multirange data types
Justin Pryzby <pryzby@telsasoft.com>
From: Justin Pryzby <pryzby@telsasoft.com>
To: Alexander Korotkov <aekorotkov@gmail.com>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>, Noah Misch <noah@leadboat.com>, Tom Lane <tgl@sss.pgh.pa.us>, Jonathan S Katz <jkatz@postgresql.org>, Zhihong Yu <zyu@yugabyte.com>, pgsql-hackers@lists.postgresql.org
Date: 2021-07-13T14:07:55Z
Lists: pgsql-hackers
On Tue, Jul 13, 2021 at 03:11:16PM +0300, Alexander Korotkov wrote: > On Sun, Jul 11, 2021 at 1:20 AM Justin Pryzby <pryzby@telsasoft.com> wrote: > > On Sun, Jul 11, 2021 at 01:00:27AM +0300, Alexander Korotkov wrote: > > > On Sat, Jul 10, 2021 at 7:34 PM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote: > > > > On 2021-Jun-27, Alexander Korotkov wrote: > > > > > > > > > BTW, I found some small inconsistencies in the declaration of > > > > > multirange operators in the system catalog. Nothing critical, but if > > > > > we decide to bump catversion in beta3, this patch is also nice to > > > > > push. > > > > > > > > Hmm, I think you should push this and not bump catversion. That way, > > > > nobody is forced to initdb if we end up not having a catversion bump for > > > > some other reason; but also anybody who initdb's with beta3 or later > > > > will get the correct descriptions. > > > > > > > > If you don't push it, everybody will have the wrong descriptions. > > > > > > True, but I'm a bit uncomfortable about user instances with different > > > catalogs but the same catversions. On the other hand, initdb's with > > > beta3 or later will be the vast majority among pg14 instances. > > > > > > Did we have similar precedents in the past? > > > > It seems so. > > > > Note in particular 74ab96a45, which adds a new function with no bump. > > Although that one may not be a good precedent to follow, or one that's been > > followed recently. > > Justin, thank you very much for the summary. > > Given we have similar precedents in the past, I'm going to push the > patch [1] to master and pg14 if no objections. To be clear, do you mean with or without this hunk ? - oprrest => 'multirangesel', oprjoin => 'scalargtjoinsel' }, + oprrest => 'multirangesel', oprjoin => 'scalarltjoinsel' }, -- Justin
Commits
-
Fix small inconsistencies in catalog definition of multirange operators
- 4d39d4e639b4 14.0 landed
- 768ea9bcf981 15.0 landed
-
Revert 29854ee8d1 due to buildfarm failures
- 817bb0a7d1e0 14.0 landed
-
Copy-edit text for the pg_terminate_backend() "timeout" parameter.
- 0aac73e6a260 14.0 cited
-
Add missing pg_description strings for pg_type entries.
- b09a64d602a1 12.0 cited
-
Fix pg_description entries for jsonb_to_record() and jsonb_to_recordset().
- a4627e8fd479 9.6.0 cited
-
docs: clarify JSONB operator descriptions
- b852dc4cbd09 9.6.0 cited
-
Set procost to 10 for each of the pg_foo_is_visible() functions.
- a80889a7359e 9.3.0 cited
-
Make use of LATERAL in information_schema.sequences view.
- c246eb5aafe6 9.3.0 cited
-
Add pg_trigger_depth() function
- 74ab96a45ef6 9.2.0 cited
-
Add database comments to template0 and postgres databases, and improve
- ddd6ff289f25 9.1.0 cited