Re: Frequent Update Project: Design Overview of HOT Updates - Mailing list pgsql-hackers

From Pavan Deolasee
Subject Re: Frequent Update Project: Design Overview of HOT Updates
Date
Msg-id 2e78013d0611100202scdcc03ke97e7166fde220e3@mail.gmail.com
Whole thread Raw
In response to Re: Frequent Update Project: Design Overview of HOT Updates  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers


On 11/10/06, Tom Lane <tgl@sss.pgh.pa.us > wrote:
"Pavan Deolasee" <pavan.deolasee@gmail.com> writes:

> Yes. The last bit in the t_infomask is used up to mark presence of overflow
> tuple header. But I believe there are few more bits that can be reused.
> There are three bits available in the t_ctid field as well (since ip_posid
> needs maximum 13 bits).

No, you cannot have those bits --- BLCKSZ is not limited to 8K, and even
if it were, we will not hold still for sticking flag bits into an
unrelated datatype.


BLCKSZ is not limited to 8K, but it is limited  to 32K because of lp_off and lp_len
which are 15 bits in size.

OffsetNumber is limited to (BLCKSZ / sizeof(ItemIdData)). Since sizeof(ItemIdData) is 4 bytes, MaxOffsetNumber is 8192. So we need only 13 bits to represent the MaxOffsetNumber.

Regards,
Pavan

pgsql-hackers by date:

Previous
From: "Simon Riggs"
Date:
Subject: Re: Frequent Update Project: Design Overview of HOT
Next
From: "Heikki Linnakangas"
Date:
Subject: Re: Frequent Update Project: Design Overview of HOT Updates