| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Florian Pflug <fgp(dot)phlo(dot)org(at)gmail(dot)com>, Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, Gregory Stark <stark(at)enterprisedb(dot)com>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: HOT patch - version 15 |
| Date: | 2007-09-10 08:17:18 |
| Message-ID: | 1189412238.4281.87.camel@ebony.site |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
On Mon, 2007-09-10 at 09:03 +0100, Heikki Linnakangas wrote:
> > As I understand it, there are two HOT features:
> >
> > Single-chain pruning, which trims HOT chains but doesn't reuse
> > the space
> >
> > Defragementation, which prunes the entire page and reuses space
> > and handles deleted rows, etc.
>
> I'm repeating myself, but I would split that second operation into two
> parts while we think about this: pruning the entire page, and
> defragmenting (PageRepairFragmentation). Tom wondered why they're
> separated in the patch. As the patch stands, there is no reason, but I
> feel that separating them and doing them at different times might be an
> important piece in the puzzle.
Yes, it does seem important to keep that separation, since it is
possible to do these things at different times, even if, for now, we
choose not to.
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | db | 2007-09-10 08:45:59 | Re: invalidly encoded strings |
| Previous Message | Gregory Stark | 2007-09-10 08:04:54 | Re: invalidly encoded strings |