Re: PG 13 release notes, first draft - Mailing list pgsql-hackers

From Etsuro Fujita
Subject Re: PG 13 release notes, first draft
Date
Msg-id CAPmGK15aejDyp7G-cnzZfobFoMRUgHEw0v7VsRV=mkxLZ+7t4Q@mail.gmail.com
Whole thread Raw
In response to Re: PG 13 release notes, first draft  (Amit Langote <amitlangote09@gmail.com>)
List pgsql-hackers
On Fri, May 8, 2020 at 12:07 PM Amit Langote <amitlangote09@gmail.com> wrote:
> On Fri, May 8, 2020 at 2:06 AM Bruce Momjian <bruce@momjian.us> wrote:
> > On Fri, May  8, 2020 at 12:32:16AM +0900, Amit Langote wrote:
> > > c8434d64c implements a new feature whereby, to use partitionwise join,
> > > partition bounds of the tables being joined no longer have to match
> > > exactly.  I think it might be better to mention this explicitly
> > > because it enables partitionwise joins to be used in more partitioning
> > > setups.
> >
> > Well, the text says:
> >
> >         Allow partitionwise joins to happen in more cases (Ashutosh Bapat,
> >         Etsuro Fujita, Amit Langote, Tom Lane)
> >
> > Isn't that what you just said?  I just added this paragraph:
> >
> >         For example, partitionwise joins can now happen between partitioned
> >         tables where the ancestors do not exactly match.
> >
> > Does that help?
>
> Yes, although "ancestors do not exactly match" doesn't make clear what
> about partitioned tables doesn't match.   "partition bounds do not
> exactly match" would.

+1 for that change.

Thank you for taking the time to this!

Best regards,
Etsuro Fujita



pgsql-hackers by date:

Previous
From: Ranier Vilela
Date:
Subject: Re: [PATCH] Fix division by zero (explain.c)
Next
From: Fujii Masao
Date:
Subject: Re: +(pg_lsn, int8) and -(pg_lsn, int8) operators