Re: Use durable_unlink for .ready and .done files for WAL segment removal

From: Nathan Bossart <bossartn(at)amazon(dot)com>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Cc: Michael Paquier <michael(at)paquier(dot)xyz>
Subject: Re: Use durable_unlink for .ready and .done files for WAL segment removal
Date: 2018-11-02 14:47:08
Message-ID: 154117002849.5569.14588306221618961668.pgcf@coridan.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

One argument for instead checking WAL file existence before calling
archive_command might be to avoid the increased startup time.
Granted, any added delay from this patch is unlikely to be noticeable
unless your archiver is way behind and archive_status has a huge
number of files. However, I have seen cases where startup is stuck on
other tasks like SyncDataDirectory() and RemovePgTempFiles() for a
very long time, so perhaps it is worth considering.

Nathan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Petr Jelinek 2018-11-02 14:51:34 Re: replication_slots usability issue
Previous Message Tom Lane 2018-11-02 14:42:21 Re: PG vs macOS Mojave