| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: WAL replay does not verify integrity |
| Date: | 2010-03-02 09:58:20 |
| Message-ID: | 4B8CE13C.5030801@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Albe Laurenz wrote:
> As demonstrated here:
> http://archives.postgresql.org/pgsql-general/2010-02/msg01057.php
>
> it can happen that you end up with a corrupt database
> if you use PITR to recover past a hardware failure.
>
> It seems that unique constraints are not verified during
> WAL replay.
>
> Is that intentional or an oversight that should be fixed?
It's intentional. WAL replay works at a lower level, it has no knowledge
of operators or the concept of uniqueness.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ivan Sergio Borgonovo | 2010-03-02 10:06:16 | Re: dedebugging and a functions that just don't work on debian flavour |
| Previous Message | Greg Stark | 2010-03-02 09:49:31 | Re: Hung postmaster (8.3.9) |