Re: concurrent COPY performance

Поиск
Список
Период
Сортировка
От Kevin Grittner
Тема Re: concurrent COPY performance
Дата
Msg-id 4A37D2F90200002500027C39@gw.wicourts.gov
обсуждение исходный текст
Ответ на Re: concurrent COPY performance  (Andrew Dunstan <andrew@dunslane.net>)
Ответы Re: concurrent COPY performance  (Gurjeet Singh <singh.gurjeet@gmail.com>)
Список pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> wrote:
> If a table is created or truncated in the same transaction that does
> the load, and archiving is not on, the COPY is not WALed.
Slightly off topic, but possibly relevant to the overall process:
those are the same conditions under which I would love to see the
rows inserted with the hint bits showing successful commit and the
transaction ID showing frozen.  We currently do a VACUUM FREEZE
ANALYZE after such a load, to avoid burdening random users with the
writes.  It would be nice not to have to write all the pages again
right after a load.
-Kevin


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

Предыдущее
От: Andrew Dunstan
Дата:
Сообщение: Re: concurrent COPY performance
Следующее
От: Stefan Kaltenbrunner
Дата:
Сообщение: Re: concurrent COPY performance