Re: Data loss, vacuum, transaction wrap-around

From: pgsql(at)mohawksoft(dot)com
To: "Russell Smith" <mr-russ(at)pws(dot)com(dot)au>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql(at)mohawksoft(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Data loss, vacuum, transaction wrap-around
Date: 2005-02-19 02:39:23
Message-ID: 16585.24.91.171.78.1108780763.squirrel@mail.mohawksoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On Sat, 19 Feb 2005 04:10 am, Tom Lane wrote:
>> pgsql(at)mohawksoft(dot)com writes:
>> > In fact, I think it is so bad, that I think we need to back-port a fix
>> to
>> > previous versions and issue a notice of some kind.
>>
>> They already do issue notices --- see VACUUM.
>>
>> A real fix (eg the forcible stop we were talking about earlier) will not
>> be reasonable to back-port.
>>
> Not to be rude, but if backporting is not an option, why do we not just
> focus on the job of getting autovacuum into 8.1, and not have to think
> about how a patch that will warn users will work?

Unless I'm mistaken, even "autovacuum" may not be enough. AFAIK,
autovacuum depends on the statistics daemon, and some admins may turn that
off for performance. Even so, how unlikely is it that autovacuum doesn't
run.

I think there should be a 100% no data loss fail safe. Anything less is a
cop-out. I can't see one successful argument that starts with data loss
and ends with maintenence.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2005-02-19 02:48:49 Re: Data loss, vacuum, transaction wrap-around
Previous Message lsunley 2005-02-19 02:10:02 Re: Data loss, vacuum, transaction wrap-around