| From: | "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com> |
|---|---|
| To: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com> |
| Cc: | "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "pgsql-patches" <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: Relation forks & FSM rewrite patches |
| Date: | 2008-07-04 19:32:06 |
| Message-ID: | 486E7AB6.40804@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Alvaro Herrera wrote:
> I wonder if we could instead make vacuum write a new FSM tree from
> scratch, rather than updating it piecemeal.
I'd like to move away from that, as we'll hopefully get some sort of
partial vacuum capability soon.
We might want to have some sort of bulk update operation, though, so
that you could refresh FSM information for say 100 pages, or one FSM
page, at a time. That would reduce the WAL traffic of a VACUUM
significantly, though I'm not sure how significant that is to begin with.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hans-Juergen Schoenig | 2008-07-05 08:43:57 | Re: WITH RECURSIVE updated to CVS TIP |
| Previous Message | Dave Page | 2008-07-04 18:38:13 | Re: Explain XML patch v2 |