Tom, I only see this in pg_clog:
[EMAIL PROTECTED] data]# ls pg_clog/ 0000
No, I had not been running Vacuum on a regular interval. :( I just added "vacuumdb --all" to my daily cron, though...
On Feb 22, 2004, at 6:04 PM, Tom Lane wrote:
"Bethany A.Benzur" <[EMAIL PROTECTED]> writes:Argg... I guess I won't be rebuilding template1 from template0 seeing as I have no template0!! :(
template1=> UPDATE pg_database SET datallowconn = TRUE template1-> WHERE datname = 'template0'; UPDATE 0
Hm. I'm beginning to think you've got a transaction counter wraparound
issue. What filenames do you have in $PGDATA/pg_clog/ ? How long has
this database been running, and have you been doing full-database
VACUUMs at regular intervals? (See the "routine maintenance" section of
the Admin Guide for background.)
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
