Postgres Pro
Downloads
Home   >   mailing lists

Re: CREATE INDEX and HOT (was Question: pg_class attributes and race conditions ?) - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: CREATE INDEX and HOT (was Question: pg_class attributes and race conditions ?)
Date
Msg-id 45FE6B4D.3070101@enterprisedb.com
Whole thread Raw
In response to Re: CREATE INDEX and HOT (was Question: pg_class attributes and race conditions ?)  ("Pavan Deolasee" <pavan.deolasee@enterprisedb.com>)
Responses Re: CREATE INDEX and HOT (was Question: pg_classattributes and race conditions ?)  ("Simon Riggs" <simon@2ndquadrant.com>)
List pgsql-hackers
Tree view 
Pavan Deolasee wrote:
> Heikki Linnakangas wrote:
>  > Pavan Deolasee wrote:
>  > We would only need the extra byte in HOT-updated tuples. 
> Alternatively, we could use the bits we have free in infomask2. There's 
> currently 5 bits free, using just 2 or 3 of those would get us quite 
> far. Or just one, which would be the Tom's suggestion of only using HOT 
> for tables with a single index.
>  >
> 
> We've already used three of those, two for tracking HEAP_ONLY
> and HOT_UPDATED tuples and one for tracking fragmented tuple.

HEAP_ONLY_TUPLE would go away in favor of the per-index bits. So we have 
bits available for three indexes.

--   Heikki Linnakangas  EnterpriseDB   http://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: "Pavan Deolasee"
Date:
Subject: Re: CREATE INDEX and HOT (was Question:pg_classattributes and race conditions ?)
Next
From: Heikki Linnakangas
Date:
Subject: Re: modifying the tbale function