Re: Inserting heap tuples in bulk in COPY

Поиск
Список
Период
Сортировка
От Jeff Janes
Тема Re: Inserting heap tuples in bulk in COPY
Дата
Msg-id CAMkU=1ywb3RHfkyB7zbNrX1WDpx5D4tT=kXjLqNpFajLBsgmZQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Inserting heap tuples in bulk in COPY  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Ответы Re: Inserting heap tuples in bulk in COPY  (Jeff Janes <jeff.janes@gmail.com>)
Список pgsql-hackers
On Mon, Oct 24, 2011 at 7:46 AM, Heikki Linnakangas
<heikki.linnakangas@enterprisedb.com> wrote:
>
> Thanks! Here's an updated version of the patch, fixing that, and all the
> other issues pointed out this far.
>
> I extracted the code that sets oid and tuple headers, and invokes the
> toaster, into a new function that's shared by heap_insert() and
> heap_multi_insert(). Tom objected to merging heap_insert() and
> heap_multi_insert() into one complicated function, and I think he was right
> on that, but sharing this code to prepare a tuple still makes sense. IMHO it
> makes heap_insert() slightly more readable too.

Hi Heikki,

Thanks for this patch.  Doing bulk copies in parallel for me is now
limited by the IO subsystem rather than the CPU.

This patch, commit number d326d9e8ea1d69, causes fillfactor to be
ignored for the copy command.  Is this acceptable collateral damage?

This can be seen by using "pgbench -i -s50 -F50" to create the table
combined with and select
pg_size_pretty(pg_table_size('pgbench_accounts')), or by using the
relation_free_space extension to pageinspect proposed elsewhere.

Thanks,

Jeff


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: Re: pg_dump vs malloc
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: xpath_table