| From: | Alexander Pyhalov <a(dot)pyhalov(at)postgrespro(dot)ru> |
|---|---|
| To: | Amit Langote <amitlangote09(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: join pushdown and issue with foreign update |
| Date: | 2021-06-01 16:00:55 |
| Message-ID: | 050b90460c024dd21af53dbaaf8fd510@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Amit Langote писал 2021-06-01 15:47:
> Perhaps, we can get away with adding the wholerow Var with the target
> relation's reltype when the target foreign table is not a "child"
> relation, but the root target relation itself. Maybe like the
> attached?
>
Hi.
I think the patch fixes this issue, but it still preserves chances to
get RECORD in fetch_more_data()
(at least with combination with asymmetric partition-wise join).
What about the following patch?
--
Best regards,
Alexander Pyhalov,
Postgres Professional
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Fix-foreign-update.patch | text/x-diff | 16.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2021-06-01 16:05:50 | Re: security_definer_search_path GUC |
| Previous Message | Joel Jacobson | 2021-06-01 15:56:43 | Re: security_definer_search_path GUC |