Re: Hot standby and synchronous replication status
От | Joshua D. Drake |
---|---|
Тема | Re: Hot standby and synchronous replication status |
Дата | |
Msg-id | 1250027706.7494.1479.camel@jd-desktop.iso-8859-1.charter.com обсуждение исходный текст |
Ответ на | Re: Hot standby and synchronous replication status (Robert Haas <robertmhaas@gmail.com>) |
Список | pgsql-hackers |
On Tue, 2009-08-11 at 17:30 -0400, Robert Haas wrote: > 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. Depends on all kinds of factors. For example, PITRTools will keep a copy local until it knows that the remote has received it. Joshua D. Drake > > ...Robert > -- PostgreSQL - XMPP: jdrake@jabber.postgresql.org Consulting, Development, Support, Training 503-667-4564 - http://www.commandprompt.com/ The PostgreSQL Company, serving since 1997
В списке pgsql-hackers по дате отправления: