| From: | hubert depesz lubaczewski <depesz(at)depesz(dot)com> |
|---|---|
| To: | Ian Harding <harding(dot)ian(at)gmail(dot)com> |
| Cc: | General PostgreSQL List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Log Apply Delay |
| Date: | 2011-09-16 15:35:43 |
| Message-ID: | 20110916153543.GB11550@depesz.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Sep 16, 2011 at 08:02:31AM -0700, Ian Harding wrote:
> Oracle has a configuration option for its version of hot standby
> (DataGuard) that lets you specify a time based delay in applying logs.
> They get transferred right away, but changes in them are only applied
> as they reach a certain age. The idea is that if something horrible
> happens on the master, you can keep it from propagating to one or more
> of your standby databases (or keep from having to reinstate one in the
> case of a failover)
>
> Anyway, Is there any plan to add a knob like that to the streaming
> replication in Postgres?
In streaming - no. But if you want delay, perhaps normal WAL-files based
approach would be good enough? OmniPITR, for one, has a option to delay
applying wal segments.
Best regards,
depesz
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ian Harding | 2011-09-16 15:41:34 | Re: Log Apply Delay |
| Previous Message | Guillaume Lelarge | 2011-09-16 15:33:17 | Re: Log Apply Delay |