Re: Failed to delete old ReorderBuffer spilled files

Поиск
Список
Период
Сортировка
От Craig Ringer
Тема Re: Failed to delete old ReorderBuffer spilled files
Дата
Msg-id CAMsr+YG31Je0e3BhiG2eQmWBPPbgG2zbH3o4r-psykOCNNu3ZQ@mail.gmail.com
обсуждение исходный текст
Ответ на Failed to delete old ReorderBuffer spilled files  (atorikoshi <torikoshi_atsushi_z2@lab.ntt.co.jp>)
Ответы Re: Failed to delete old ReorderBuffer spilled files
Список pgsql-hackers
On 20 November 2017 at 18:35, atorikoshi <torikoshi_atsushi_z2@lab.ntt.co.jp> wrote:
Hi,

I put many queries into one transaction and made ReorderBuffer spill
data to disk, and sent SIGKILL to postgres before the end of the
transaction.

After starting up postgres again, I observed the files spilled to
data wasn't deleted.

Since this can only happen  on crash exits, and the reorderbuffer data is useless after a decoding backend exits, why don't we just recursively delete the tree contents on Pg startup?

--
 Craig Ringer                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

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

Предыдущее
От: Kyotaro HORIGUCHI
Дата:
Сообщение: Re: Failed to delete old ReorderBuffer spilled files
Следующее
От: Craig Ringer
Дата:
Сообщение: Re: Logical Replication and triggers