Re: autovacuum next steps, take 2 - Mailing list pgsql-hackers

From Tom Lane
Subject Re: autovacuum next steps, take 2
Date
Msg-id 10387.1172548129@sss.pgh.pa.us
Whole thread Raw
In response to Re: autovacuum next steps, take 2  ("Matthew T. O'Connor" <matthew@zeut.net>)
Responses Re: autovacuum next steps, take 2  ("Matthew T. O'Connor" <matthew@zeut.net>)
Re: autovacuum next steps, take 2  ("Jim C. Nasby" <jim@nasby.net>)
List pgsql-hackers
"Matthew T. O'Connor" <matthew@zeut.net> writes:
> That does sounds simpler. Is chunk-at-a-time a realistic option for 8.3?

It seems fairly trivial to me to have a scheme where you do one
fill-workmem-and-scan-indexes cycle per invocation, and store the
next-heap-page-to-scan in some handy place (new pg_class column updated
along with relpages/reltuples, likely).  Galy is off in left field with
some far more complex ideas :-( but I don't see that there's all that
much needed to support this behavior ... especially if we don't expose
it to the SQL level but only support it for autovac's use.  Then we're
not making any big commitment to support the behavior forever.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Rusty Conover
Date:
Subject: Expanding DELETE/UPDATE returning
Next
From: "Matthew T. O'Connor"
Date:
Subject: Re: autovacuum next steps, take 2