| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Tom Lanyon <tom+pgsql-hackers(at)oneshoeco(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: 8.4 path to repair_frag()? |
| Date: | 2012-04-18 16:03:07 |
| Message-ID: | 1334764943-sup-2167@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Excerpts from Tom Lanyon's message of mié abr 18 12:44:11 -0300 2012:
> Hi all,
>
> To satisfy my own curiosity, I was trying to find where 8.4 kicks into a backwards scan of the data file during (auto-)vacuuming.
>
> This appears to be repair_frag() in backend/commands/vacuum.c, but only appears to be called by a FULL vacuum. Autovacuum, however, appears to explicitly only ever call a not-FULL vacuum, so I'm trying to see where and how it would be possible for autovacuum to trigger this operation. Any pointers?
See lazy_truncate_heap in vacuumlazy.c.
--
Á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 | Robert Haas | 2012-04-18 16:05:03 | Re: Bug #6593, extensions, and proposed new patch policy |
| Previous Message | Flavio Vodzinski | 2012-04-18 16:00:10 | Postgres install program files folder |