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

From Andrey Lepikhov
Subject Re: join pushdown and issue with foreign update
Date
Msg-id f0e58ebd-e5e6-e905-f3ab-a609272e6f08@postgrespro.ru
Whole thread Raw
In response to Re: join pushdown and issue with foreign update  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: join pushdown and issue with foreign update
List pgsql-hackers
On 2/6/21 02:32, Tom Lane wrote:
> I wrote:
>> I think a preferable fix involves making sure that the correct
>> record-type typmod is propagated to record_in in this context.
>> Alternatively, maybe we could insert the foreign table's rowtype
>> during execution of the input operation, without touching the
>> plan as such.
> 
> Here's a draft-quality patch based on that idea.  It resolves
> the offered test case, but I haven't beat on it beyond that.
> 
>             regards, tom lane
> 
I played with your patch and couldn't find any errors. But what if ROW 
operation were allowed to be pushed to a foreign server?
Potentially, I can imagine pushed-down JOIN with arbitrary ROW function 
in its target list.
Amit's approach looks more safe for me.

-- 
regards,
Andrey Lepikhov
Postgres Professional



pgsql-hackers by date:

Previous
From: "houzj.fnst@fujitsu.com"
Date:
Subject: RE: Parallel INSERT SELECT take 2
Next
From: Amit Langote
Date:
Subject: Re: join pushdown and issue with foreign update