Re: Another way to fix inherited UPDATE/DELETE - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Another way to fix inherited UPDATE/DELETE
Date
Msg-id 14617.1550640113@sss.pgh.pa.us
Whole thread Raw
In response to Re: Another way to fix inherited UPDATE/DELETE  (Pavan Deolasee <pavan.deolasee@gmail.com>)
List pgsql-hackers
Pavan Deolasee <pavan.deolasee@gmail.com> writes:
> We will need to consider how this affects EvalPlanQual which currently
> doesn't have to do anything special for partitioned tables. I solved that
> via tracking the expanded-at-the-bottom child in a separate
> mergeTargetRelation, but that approach has been criticised. May be Tom's
> idea doesn't have the same problem or most likely he will have a far better
> approach to address that.

I did spend a few seconds thinking about that, and my gut says that
this wouldn't change anything interesting for EPQ.  But the devil
is in the details as always, so maybe working out the patch would
find problems ...

            regards, tom lane


pgsql-hackers by date:

Previous
From: Pavan Deolasee
Date:
Subject: Re: Another way to fix inherited UPDATE/DELETE
Next
From: "Tsunakawa, Takayuki"
Date:
Subject: RE: Speed up transaction completion faster after many relations areaccessed in a transaction