| From: | Doug McNaught <doug(at)mcnaught(dot)org> |
|---|---|
| To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Kouber Saparev <postgresql(at)saparev(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Help me recovering data |
| Date: | 2005-02-14 17:56:45 |
| Message-ID: | 873bvzja8y.fsf@asmodeus.mcnaught.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | pgsql | 2005-02-14 17:59:49 | Re: Help me recovering data |
| Previous Message | Ron Mayer | 2005-02-14 17:55:38 | Re: Query optimizer 8.0.1 (and 8.0) |