From: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
---|---|
To: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com> |
Cc: | Martijn van Oosterhout <kleptog(at)svana(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Free space management within heap page |
Date: | 2007-01-23 09:33:28 |
Message-ID: | 45B5D668.5050406@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Pavan Deolasee wrote:
> One assumption I am making here is that its sufficient to mark the line
> pointer
> "unused" (reset LP_USED flag) even though there is an index entry pointing
> to
> the tuple. During index scan, we anyways check for ItemIdIsUsed() before
> proceeding further. I know it might break the ctid chain, but does that
> really
> matter ? I don't see any reason why somebody would need to follow ctid
> chain
> past a dead tuple.
You can't clear the LP_USED flag, but you could use the LP_DELETE flag
that's currently not used in heap pages.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2007-01-23 09:37:30 | Re: Free space management within heap page |
Previous Message | ITAGAKI Takahiro | 2007-01-23 09:28:55 | Re: Free space management within heap page |