Re: unnesting multirange data types
| От | Alexander Korotkov |
|---|---|
| Тема | Re: unnesting multirange data types |
| Дата | |
| Msg-id | CAPpHfdsRMh8ZepARSFs1yps3xPnUEWnmWzjhJqm6vccesrwJyA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: unnesting multirange data types (Tom Lane <tgl@sss.pgh.pa.us>) |
| Список | pgsql-hackers |
On Sun, Jul 11, 2021 at 1:28 AM Tom Lane <tgl@sss.pgh.pa.us> wrote: > Justin Pryzby <pryzby@telsasoft.com> writes: > > On Sun, Jul 11, 2021 at 01:00:27AM +0300, Alexander Korotkov wrote: > >> 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. > > If it's *only* the description strings you want to change, then yeah, > we've done that before. My patch also changes 'oprjoin' from 'scalargtjoinsel' to 'scalarltjoinsel'. Implementation is the same, but 'scalarltjoinsel' looks more logical here. ------ Regards, Alexander Korotkov
В списке pgsql-hackers по дате отправления: