"Luki Rustianto" <[EMAIL PROTECTED]> 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 ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
