summaryrefslogtreecommitdiff
path: root/meson_options.txt
diff options
context:
space:
mode:
authorEtsuro Fujita <efujita@postgresql.org>2022-12-20 19:05:00 +0900
committerEtsuro Fujita <efujita@postgresql.org>2022-12-20 19:05:00 +0900
commit594f8d3776af4699c5c32443b9d6a486f44beabf (patch)
treed2df5db6ab1174358eaab8bb5f6ee0dd7623086f /meson_options.txt
parent3226f47282a05979483475d1e4a11aab8c1bfc39 (diff)
downloadpostgresql-594f8d3776af4699c5c32443b9d6a486f44beabf.tar.gz
Allow batching of inserts during cross-partition updates.
Commit 927f453a9 disallowed batching added by commit b663a4136 to be used for the inserts performed as part of cross-partition updates of partitioned tables, mainly because the previous code in nodeModifyTable.c couldn't handle pending inserts into foreign-table partitions that are also UPDATE target partitions. But we don't have such a limitation anymore (cf. commit ffbb7e65a), so let's allow for this by removing from execPartition.c the restriction added by commit 927f453a9 that batching is only allowed if the query command type is CMD_INSERT. In postgres_fdw, since commit 86dc90056 changed it to effectively disable cross-partition updates in the case where a foreign-table partition chosen to insert rows into is also an UPDATE target partition, allow batching in the case where a foreign-table partition chosen to do so is *not* also an UPDATE target partition. This is enabled by the "batch_size" option added by commit b663a4136, which is disabled by default. This patch also adjusts the test case added by commit 927f453a9 to confirm that the inserts performed as part of a cross-partition update of a partitioned table indeed uses batching. Amit Langote, reviewed and/or tested by Georgios Kokolatos, Zhihong Yu, Bharath Rupireddy, Hou Zhijie, Vignesh C, and me. Discussion: http://postgr.es/m/CA%2BHiwqH1Lz1yJmPs%3DaD-pzd_HLLynLHvq5iYeT9mB0bBV7oJ6w%40mail.gmail.com
Diffstat (limited to 'meson_options.txt')
0 files changed, 0 insertions, 0 deletions