Re: Automatic free space map filling
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Jim C. Nasby" <jnasby@pervasive.com>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>, Alvaro Herrera <alvherre@commandprompt.com>, Csaba Nagy <nagy@ecircle-ag.com>, "Matthew T. O'Connor" <matthew@zeut.net>, Christopher Browne <cbbrowne@acm.org>, postgres hackers <pgsql-hackers@postgresql.org>
Date: 2006-05-01T18:35:24Z
Lists: pgsql-hackers
"Jim C. Nasby" <jnasby@pervasive.com> writes: >>> Alvaro Herrera <alvherre@commandprompt.com> writes: >>>> So for you it would certainly help a lot to be able to vacuum the first >>>> X pages of the big table, stop, release locks, create new transaction, >>>> continue with the next X pages, lather, rinse, repeat. >>> Bruce and I were discussing this the other day; it'd be pretty easy to >>> make plain VACUUM start a fresh transaction immediately after it >>> finishes a scan heap/clean indexes/clean heap cycle. > Except that wouldn't help when vacuuming a lot of small tables; each one > would get it's own transaction. What's your point? There's only a problem for big tables, and VACUUM already does use a new transaction for each table. regards, tom lane