Re: Re: Synch Rep: direct transfer of WAL file from the primary to the standby - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Re: Synch Rep: direct transfer of WAL file from the primary to the standby
Date
Msg-id 14360.1246893386@sss.pgh.pa.us
Whole thread Raw
In response to Re: Synch Rep: direct transfer of WAL file from the primary to the standby  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: Re: Synch Rep: direct transfer of WAL file from the primary to the standby  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-hackers
Fujii Masao <masao.fujii@gmail.com> writes:
> In order for the primary server (ie. a normal backend) to read an archived file,
> restore_command needs to be specified in also postgresql.conf. In this case,
> how should we handle restore_command in recovery.conf?

I confess to not having paid much attention to this thread so far, but ...
what is the rationale for having such a capability at all?  It seems to
me to be exposing implementation details that we do not need to expose,
as well as making assumptions that we shouldn't make (like there is
exactly one archive and the primary server has read access to it).
        regards, tom lane


pgsql-hackers by date:

Previous
From: David Fetter
Date:
Subject: Re: First CommitFest: July 15th
Next
From: Bruce Momjian
Date:
Subject: Re: First CommitFest: July 15th