On Friday, July 29, 2011 1:23:55 am Raghavendra wrote:
> On Fri, Jul 29, 2011 at 1:42 PM, Toby Corkindale <
>
> toby.corkindale@strategicdata.com.au> wrote:
> > Hi,
> > In the repmgr README, it suggests configuration should include:
> >
> > archive_mode = on
> > archive_command = 'cd .'
> >
> > Could someone explain why we need archive_mode enabled? In my own testing
> > of Pg's streaming replication, I've found it to work without this
> > enabled.
>
> AFAIK, enabling 'archive_mode' parameter turns the cluster into Archive-log
> Mode and generates a copy of WAL segements to ARCHIVE destination.
>
> Strange to know that Streaming replication done without this parameter,
> could you share the output of the below command in the PRIMARY cluster.
Not really, it just means that the WAL segments are not stored once they leave
the the primary. Think of it as a |.
>
> show archive_mode
> show archive_command
>
> ---
> Regards,
> Raghavendra
> EnterpriseDB Corporation
> Blog: http://raghavt.blogspot.com/
--
Adrian Klaver
adrian.klaver@gmail.com
