| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | David Steele <david(at)pgmasters(dot)net>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_upgrade and rsync |
| Date: | 2015-01-27 00:10:21 |
| Message-ID: | 54C6D76D.3050000@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1/26/15 5:08 PM, David Steele wrote:
> I've written tests to show the rsync vulnerability and another to show
> that this can affect a running database. However, to reproduce it
> reliably you need to force a checkpoint or have them happening pretty
> close together.
Related to this and Stephen's comment about testing... ISTM it would be very useful to have a published suite of tests for PITR backups, perhaps even utilizing special techniques in Postgres to expose potential failure conditions. Similarly, it'd also be nice to have a suite of tests you could run to validate a backup that you've restored.
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2015-01-27 00:11:48 | Re: Shortcoming in CLOBBER_FREED_MEMORY coverage: disk buffer pointers |
| Previous Message | Jim Nasby | 2015-01-27 00:03:02 | Re: Shortcoming in CLOBBER_FREED_MEMORY coverage: disk buffer pointers |