| From: | Amit Langote <amitlangote09(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, David Rowley <dgrowleyml(at)gmail(dot)com>, "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> |
| Subject: | Re: ModifyTable overheads in generic plans |
| Date: | 2020-10-30 06:13:46 |
| Message-ID: | CA+HiwqEuMDfduYDuP+qxEpka6-+5u-2GNBfL-DcUGxxj0vC-cg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Attached updated patches based on recent the discussion at:
* Re: partition routing layering in nodeModifyTable.c *
https://www.postgresql.org/message-id/CA%2BHiwqHpmMjenQqNpMHrhg3DRhqqQfby2RCT1HWVwMin3_5vMA%40mail.gmail.com
0001 adjusts how ForeignScanState.resultRelInfo is initialized for use
by direct modify operations.
0002 refactors ResultRelInfo initialization do be don lazily on first use
I call these v6, because the last version posted on this thread was
v5, even though it went through a couple of iterations on the above
thread. Sorry about the confusion.
--
Amit Langote
EDB: http://www.enterprisedb.com
| Attachment | Content-Type | Size |
|---|---|---|
| v6-0001-Call-BeginDirectModify-from-ExecInitModifyTable.patch | application/octet-stream | 3.8 KB |
| v6-0002-Initialize-result-relation-information-lazily.patch | application/octet-stream | 65.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2020-10-30 06:20:36 | Re: Enumize logical replication message actions |
| Previous Message | Amit Langote | 2020-10-30 06:06:50 | Re: partition routing layering in nodeModifyTable.c |