| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Luki Rustianto" <lukirus(at)gmail(dot)com> |
| Cc: | "General PostgreSQL List" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: DB crashed and duplicated template0 db |
| Date: | 2007-07-06 16:21:27 |
| Message-ID: | 6008.1183738887@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Luki Rustianto" <lukirus(at)gmail(dot)com> writes:
> One of my customer's server goes down, I don't know yet how, but when
> when they restart the machine I got this:
> 1. DB is working like usual
> 2. template0 and template1 database is *duplicated*
> 3. I can't do pg_dump, because error returned (see below)
This looks a bit like transaction ID wraparound causing old dead
versions of rows to reappear as live. What's the vacuuming policy
been on this database?
See recent discussion of a similar symptom here
http://archives.postgresql.org/pgsql-admin/2007-07/msg00037.php
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rupesh Bajaj | 2007-07-06 18:04:53 | Implementation of three new operators inside the PostgreSQL |
| Previous Message | Alvaro Herrera | 2007-07-06 16:06:41 | Re: Problem with autovacuum and pg_autovacuum |