Re: unnesting multirange data types
| От | Alvaro Herrera |
|---|---|
| Тема | Re: unnesting multirange data types |
| Дата | |
| Msg-id | 202106151728.5kbtjl7or3g2@alvherre.pgsql обсуждение исходный текст |
| Ответ на | Re: unnesting multirange data types (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: unnesting multirange data types
Re: unnesting multirange data types |
| Список | pgsql-hackers |
On 2021-Jun-15, Tom Lane wrote: > It looks to me like the proximate problem is that you should > have taught pg_dump to skip these new auto-generated functions. > However, I fail to see why we need auto-generated functions > for this at all. Couldn't we have done it with one polymorphic > function? I think such a function would need to take anycompatiblerangearray, which is not something we currently have. > I think this ought to be reverted and reviewed more carefully. It seems to me that removing the cast-to-range[] is a sufficient fix, and that we can do with only the unnest part for pg14; the casts can be added in 15 (if at all). That would mean reverting only half the patch. -- Álvaro Herrera 39°49'30"S 73°17'W
В списке pgsql-hackers по дате отправления: