| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | Ygor Degani <ygordegani(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Duplicated Keys in PITR |
| Date: | 2009-08-20 16:04:49 |
| Message-ID: | 407d949e0908200904t63094c39j6fe99412650f0d26@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Aug 20, 2009 at 4:13 PM, Ygor Degani<ygordegani(at)gmail(dot)com> wrote:
> When recover a database using a continuous archive backup, i detected some
> duplicated keys. This there isn't in the production database.
> I use postgres-8.3.5.
> anyone know why this happens?
Uhm, well it's not supposed to. Do you have more information?
How are your duplicate keys being generated? Is there a unique index on them?
Are the keys there if you use a sequential scan or only if you use an
index to look them up?
Have you been running 8.3.5 the whole time or were you running older
8.3 releases for some of the time? Why aren't you running 8.3.7 --
there are known bugs in 8.3.5 though none which look to be related.
How long has the archive been running, is it feasible to give someone
the backup and complete archives going back to when it was taken?
Can you dump the pages with the bad keys using the pageinspect contrib
module? Do you need instructions on how to do that?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-08-20 16:23:48 | Re: Multi-pass planner |
| Previous Message | Tom Lane | 2009-08-20 16:03:27 | Re: explain root element for auto-explain |