Christopher Kings-Lynne <[EMAIL PROTECTED]> writes: > This might seem like a stupid question, but since this is a massive > data loss potential in PostgreSQL, what's so hard about having the > checkpointer or something check the transaction counter when it runs > and either issue a db-wide vacuum if it's about to wrap, or simply > disallow any new transactions?
I think autovac-in-backend is the preferred solution to this, and it's definitely on the TODO list... -Doug ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
