Re: Minimally avoiding Transaction Wraparound in VLDBs

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Minimally avoiding Transaction Wraparound in VLDBs
Date: 2005-09-01 09:29:56
Message-ID: 1125566996.3956.150.camel@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 2005-08-31 at 22:21 -0400, Tom Lane wrote:
> Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> > On Wed, 2005-08-31 at 19:24 -0400, Tom Lane wrote:
> >> If you don't remove any tuples,
> >> you don't scan the indexes anyway IIRC.
>
> > No. Even if you remove *zero* tuples, an index is still scanned twice.
> > Once to not delete the rows and once to not delete the pages.
>
> Yeah? Well, that could probably be improved with a less intrusive fix,
> that is, one that does it automatically instead of involving the user.
>
> I really really do not like proposals to introduce still another kind
> of VACUUM. We have too many already; any casual glance through the
> archives will show that most PG users don't have a grip on when to use
> VACUUM FULL vs VACUUM. Throwing in some more types will make that
> problem exponentially worse.

I'll post my proposal for changing that, so we can see the two
alternatives. I'm easy either way at the moment.

Best Regards, Simon Riggs

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Martijn van Oosterhout 2005-09-01 09:33:42 Re: On hardcoded type aliases and typmod for user types
Previous Message Dennis Bjorklund 2005-09-01 09:18:04 Re: On hardcoded type aliases and typmod for user types