Re: Hot standby and synchronous replication status - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Hot standby and synchronous replication status
Date
Msg-id 603c8f070908111430l1dac7c44gb3423103a1ecd1e8@mail.gmail.com
Whole thread Raw
In response to Re: Hot standby and synchronous replication status  (Dimitri Fontaine <dfontaine@hi-media.com>)
Responses Re: Hot standby and synchronous replication status  (Dimitri Fontaine <dfontaine@hi-media.com>)
Re: Hot standby and synchronous replication status  ("Joshua D. Drake" <jd@commandprompt.com>)
Re: Hot standby and synchronous replication status  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-hackers
On Tue, Aug 11, 2009 at 5:20 PM, Dimitri Fontaine<dfontaine@hi-media.com> wrote:
> We should somehow provide a default archive and restore command integrated
> into the main product, so that it's as easy as turning it 'on' in the
> configuration for users to have something trustworthy: PostgreSQL will keep
> past logs into a pg_xlog/archives subdir or some other default place, and
> will know about the setup at startup time when/if needed.

I might be missing something, but isn't this completely silly?  If you
archive your logs to the same partition where you keep your database
cluster, it seems to me that you might as well delete them.  Even
better, turn off XLogArchiving altogether and save yourself the
overhead of not using WAL-bypass.

...Robert


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: dependencies for generated header files
Next
From: Robert Haas
Date:
Subject: Re: Any tutorial or FAQ on building an extension?