Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Excerpts from Tom Lane's message of jue ago 05 13:19:41 -0400 2010:
>> In any case, the removal of VACUUM FULL didn't completely disable
>> shrinking of btree indexes did it? I don't recall having removed
> I see no call to RelationTruncate in the btvacuumscan code, but then it
> was only called in vacuum full before. I'm not sure how it worked
> previously with only lazy vacuum. Did we simply leave the pages as free
> for a later extension?
You're right, I misremembered. That code is just plain gone in 9.0:
Still, we have a live issue with heap truncation during plain VACUUM.
However, the scope of the problem seems a lot less than I was thinking.
Maybe write-the-buffers-first is a sufficient longterm solution.
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: Robert Haas||Date: 2010-08-05 18:02:44|
|Subject: Re: Two different methods of sneaking non-immutable data into an index|
|Previous:||From: Josh Berkus||Date: 2010-08-05 17:58:30|
|Subject: Re: pg_stat_user_functions' notion of user|
pgsql-bugs by date
|Next:||From: Tom Lane||Date: 2010-08-05 18:25:35|
|Subject: Re: [HACKERS] Drop one-argument string_agg? (was Re: string_agg delimiter having no effect with order by) |
|Previous:||From: Alvaro Herrera||Date: 2010-08-05 17:41:01|
|Subject: Re: BUG #5599: Vacuum fails due to index corruption issues|