| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr> |
| Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: DeArchiver process |
| Date: | 2011-11-04 11:14:10 |
| Message-ID: | CA+U5nMJrcn_fn4z-P=-tV9VyvrReBWf9BSJ-+-=5PgHVoiQVVA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Nov 4, 2011 at 11:08 AM, Dimitri Fontaine
<dimitri(at)2ndquadrant(dot)fr> wrote:
> Fujii Masao <masao(dot)fujii(at)gmail(dot)com> writes:
>> If we introduce "walrestore" process, pg_standby seems no longer useful.
>
> pg_standby is one possible restore_command, right? I had understood
> that walrestore would be the process that cares for running that
> command, not another implementation of it.
Yes, that was the idea.
> That said, I would really like us to provide a default restore command,
> so if you had any intend of handling the restoring command in the
> walrestore process, by all means, go ahead :)
A different proposal, I think. Not no, just not here and now.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Florian Pflug | 2011-11-04 11:15:56 | Re: Term positions in GIN fulltext index |
| Previous Message | Dimitri Fontaine | 2011-11-04 11:08:10 | Re: DeArchiver process |