Re: unnesting multirange data types - Mailing list pgsql-hackers

From Alexander Korotkov
Subject Re: unnesting multirange data types
Date
Msg-id CAPpHfdv7q8GN=W9jHLNABEqVWG6J52Y0R7k_jnqEZO44jX=4Fw@mail.gmail.com
Whole thread Raw
In response to Re: unnesting multirange data types  (Alexander Korotkov <aekorotkov@gmail.com>)
Responses Re: unnesting multirange data types
List pgsql-hackers
On Thu, Jun 17, 2021 at 7:54 PM Alexander Korotkov <aekorotkov@gmail.com> wrote:
> On Wed, Jun 16, 2021 at 3:44 PM Alexander Korotkov <aekorotkov@gmail.com> wrote:
> > On Tue, Jun 15, 2021 at 8:18 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > > Alexander Korotkov <aekorotkov@gmail.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.
>
> Here is the next revision of the patch: I've adjusted some comments.
>
> In my point of view this patch is not actually complex.  The reason
> why it colored buildfarm in red is purely my fault: I messed up with
> "make check-world" :(
>
> I've registered it on the commitfest application to make it go through
> commitfest.cputube.org.  My proposal is to re-push it once it goes
> through commitfest.cputube.org.

Patch successfully passed commitfest.cputube.org.  I'm going to
re-push it if there are no objections.

------
Regards,
Alexander Korotkov



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Centralizing protective copying of utility statements
Next
From: Robert Haas
Date:
Subject: Re: Add version macro to libpq-fe.h