Re: ATTACH/DETACH PARTITION CONCURRENTLY - Mailing list pgsql-hackers

From David Rowley
Subject Re: ATTACH/DETACH PARTITION CONCURRENTLY
Date
Msg-id CAKJS1f_+3k8AmtRCCUvFMh-a648KW-p22oszbH4EvQnNzd9K=A@mail.gmail.com
Whole thread Raw
In response to Re: ATTACH/DETACH PARTITION CONCURRENTLY  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: ATTACH/DETACH PARTITION CONCURRENTLY
List pgsql-hackers
On Sat, 2 Feb 2019 at 09:31, Robert Haas <robertmhaas@gmail.com> wrote:
> After having written this code, I'm still torn about whether to go
> further with this design.  On the one hand, this is such boilerplate
> code that it's kinda hard to imagine it having too many more bugs; on
> the other hand, as you can see, it's a non-trivial amount of code to
> add without a real clear reason, and I'm not sure we have one, even
> though in the abstract it seems like a better way to go.

I think we do need to ensure that the PartitionDesc matches between
worker and leader. Have a look at choose_next_subplan_for_worker() in
nodeAppend.c. Notice that a call is made to
ExecFindMatchingSubPlans().


-- 
 David Rowley                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Ryu floating point output patch
Next
From: Lætitia Avrot
Date:
Subject: Re: [Patch] Log10 and hyperbolic functions for SQL:2016 compliance