| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Enforcing that all WAL has been replayed after restoring from backup |
| Date: | 2011-08-09 15:20:33 |
| Message-ID: | 1312903147-sup-1603@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Excerpts from Heikki Linnakangas's message of mar ago 09 05:00:00 -0400 2011:
> I think this is a nice additional safeguard to have, making streamed
> backups more robust. I'd like to add this to 9.1, but it required an
> extra field to be added to the control file, so it would force an
> initdb. It's probably not worth that. Or, we could sneak in the extra
> boolean field to some currently unused pad space in the ControlFile struct.
How about making the new backup_label field optional? If absent, assume
current behavior.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2011-08-09 15:22:05 | Re: Enforcing that all WAL has been replayed after restoring from backup |
| Previous Message | Alvaro Herrera | 2011-08-09 15:04:31 | Re: Compiler warnings with stringRelOpts (was WIP: Fast GiST index build) |