| From: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com> |
|---|---|
| To: | Benedikt Grundmann <bgrundmann(at)janestreet(dot)com> |
| Cc: | Samrat Revagade <revagade(dot)samrat(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Patch for fail-back without fresh backup |
| Date: | 2013-06-14 11:09:04 |
| Message-ID: | CABOikdOeix_kxCAj_YKow+Odx89rVxGgWqbHG2V6TBRkPUQRnA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jun 14, 2013 at 2:51 PM, Benedikt Grundmann <
bgrundmann(at)janestreet(dot)com> wrote:
>
> A alternative proposal (which will probably just reveal my lack of
> understanding about what is or isn't possible with WAL). Provide a way to
> restart the master so that it rolls back the WAL changes that the slave
> hasn't seen.
>
WAL records in PostgreSQL can only be used for physical redo. They can not
be used for undo. So what you're suggesting is not possible though I am
sure a few other databases do that.
Thanks,
Pavan
--
Pavan Deolasee
http://www.linkedin.com/in/pavandeolasee
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2013-06-14 11:20:02 | Re: Patch for fail-back without fresh backup |
| Previous Message | Pavan Deolasee | 2013-06-14 11:06:38 | Re: Patch for fail-back without fresh backup |