| From: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Zhihong Yu <zyu(at)yugabyte(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: unnesting multirange data types |
| Date: | 2021-06-16 12:44:29 |
| Message-ID: | CAPpHfduCV04Wipnz0Z1gKBNwM0+FYPMOEvknWvoMiQ4KY7PytQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jun 15, 2021 at 8:18 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Alexander Korotkov <aekorotkov(at)gmail(dot)com> writes:
> > I did run "check-world", but it passed for me. Probably the same
> > reason it passed for some buildfarm animals...
>
> It looks to me like the proximate problem is that you should
> have taught pg_dump to skip these new auto-generated functions.
Yes, it appears that pg_dump skips auto-generated functions, but
doesn't skip auto-generated casts. It appears to be enough to tune
query getCasts() to resolve the issue. The revised patch is attached.
------
Regards,
Alexander Korotkov
| Attachment | Content-Type | Size |
|---|---|---|
| multirange_unnest_cast_to_array-v5.patch | application/octet-stream | 22.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2021-06-16 13:19:51 | Re: Duplicate history file? |
| Previous Message | houzj.fnst@fujitsu.com | 2021-06-16 12:40:25 | RE: [bug?] Missed parallel safety checks, and wrong parallel safety |