Re: join pushdown and issue with foreign update - Mailing list pgsql-hackers

From Tom Lane
Subject Re: join pushdown and issue with foreign update
Date
Msg-id 2850299.1622577694@sss.pgh.pa.us
Whole thread Raw
In response to Re: join pushdown and issue with foreign update  (Alexander Pyhalov <a.pyhalov@postgrespro.ru>)
List pgsql-hackers
Alexander Pyhalov <a.pyhalov@postgrespro.ru> writes:
> Tom Lane писал 2021-06-01 21:19:
>> ISTM that using a specific rowtype rather than RECORD would be
>> quite disastrous from the standpoint of bloating the number of
>> distinct resjunk columns we need for a partition tree with a
>> lot of children.  Maybe we'll have to go that way, but it seems
>> like an absolute last resort.

> Why do you think they are distinct?
> In suggested patch all of them will have type of the common ancestor 
> (root of the partition tree).

Seems moderately unlikely that that will work in cases where the
partition children have rowtypes different from the ancestor
(different column order etc).  It'll also cause the problem we
originally sought to avoid for selects across traditional inheritance
trees, where there isn't a common partition ancestor.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: CALL versus procedures with output-only arguments
Next
From: Robert Haas
Date:
Subject: Re: Race condition in recovery?