Re: Data loss, vacuum, transaction wrap-around

From: "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql(at)mohawksoft(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Data loss, vacuum, transaction wrap-around
Date: 2005-02-18 17:45:14
Message-ID: 421629AA.70406@zeut.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.
>

I hope this question isn't too stupid....

Is it be possible to create a "vacuum wraparound" or "vacuum xidreset"
command which would do the work required to fix the wraparound problem,
without being as expensive as a normal vacuum of an entire database?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message pgsql 2005-02-18 18:00:39 Re: Data loss, vacuum, transaction wrap-around
Previous Message Tom Lane 2005-02-18 17:10:09 Re: Data loss, vacuum, transaction wrap-around