Re: DeArchiver process - Mailing list pgsql-hackers

From Dimitri Fontaine
Subject Re: DeArchiver process
Date
Msg-id m2ipn2v6eb.fsf@2ndQuadrant.fr
Whole thread Raw
In response to DeArchiver process  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: DeArchiver process
List pgsql-hackers
Simon Riggs <simon@2ndQuadrant.com> writes:
> My solution is to create a new process called the DeArchiver. This
> will run restore_command in a tight loop until the number of files
> would exceed wal_keep_files, then sleep. Each time the DeArchiver
> executes restore_command it will set the return code and if rc=0 the
> new XLogRecPtr reached. If standby_mode = on it will continue to retry
> indefinitely.

+1

I think you mean wal_keep_segments, a GUC that we already have.

> Which do we prefer "DeArchiver", "Restore process", or "WALFileReceiver".

The only part of your proposal that I don't like is the process name,
that "deArchiver" thing.  "wal restore process" or something like that
would be better.  We already have "wal writer process" and "wal sender
process" and "wal receiver process".

Regards,
-- 
Dimitri Fontaine
http://2ndQuadrant.fr     PostgreSQL : Expertise, Formation et Support


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: DeArchiver process
Next
From: Robert Haas
Date:
Subject: heap_page_prune comments