From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Hitesh Bhambhani <hitesh(dot)bhambhani(at)asg(dot)com>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #5599: Vacuum fails due to index corruption issues |
Date: | 2010-08-05 17:41:01 |
Message-ID: | 1281029938-sup-3072@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
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
> that.
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?
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-08-05 18:01:15 | Re: BUG #5599: Vacuum fails due to index corruption issues |
Previous Message | Pavel Stehule | 2010-08-05 17:30:19 | Re: string_agg delimiter having no effect with order by |
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2010-08-05 17:44:52 | remove upsert example from docs |
Previous Message | Kevin Grittner | 2010-08-05 17:40:21 | Re: Concurrent MERGE |