| From: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Enforcing that all WAL has been replayed after restoring from backup |
| Date: | 2011-08-12 21:10:27 |
| Message-ID: | m2fwl672v0.fsf@2ndQuadrant.fr |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Magnus Hagander <magnus(at)hagander(dot)net> writes:
>>> Or add a signal
>>> handler in the pg_basebackup client emitting a warning about it?
>>
>> We don't have such a signal handler pg_dump either. I don't think we should
>> add it.
>
> Hmm. I guess an aborted pg_dump will also "look ok but actually be
> corrupt" (or incomplete). Good point.
What about having the signal handler corrupt the backup by adding some
garbage into it? Now the failure case is obvious…
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2011-08-12 21:17:07 | Re: Inserting heap tuples in bulk in COPY |
| Previous Message | Andrew Dunstan | 2011-08-12 21:10:11 | Re: Inserting heap tuples in bulk in COPY |