On Tue, Nov 10, 2020 at 3:47 PM Paul Guo <gu...@vmware.com> wrote: > > Thanks for doing this. There might be another solution - use raw insert > interfaces (i.e. raw_heap_insert()). > Attached is the test (not formal) patch that verifies this idea. > raw_heap_insert() writes the page into the > table files directly and also write the FPI xlog when the tuples filled up > the whole page. This seems be > more efficient. >
Thanks. Will the new raw_heap_insert() APIs scale well (i.e. extend the table parallelly) with parallelism? The existing table_multi_insert() API scales well, see, for instance, the benefit with parallel copy[1] and parallel multi inserts in CTAS[2]. [1] - https://www.postgresql.org/message-id/CALj2ACWeQVd-xoQZHGT01_33St4xPoZQibWz46o7jW1PE3XOqQ%40mail.gmail.com [2] - https://www.postgresql.org/message-id/CALj2ACWFq6Z4_jd9RPByURB8-Y8wccQWzLf%2B0-Jg%2BKYT7ZO-Ug%40mail.gmail.com With Regards, Bharath Rupireddy. EnterpriseDB: http://www.enterprisedb.com
