Skip site navigation (1) Skip section navigation (2)

toast by chunk-end (was Re: PG_PAGE_LAYOUT_VERSION 5 - time forchange)

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
Cc: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Gregory Stark <stark(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: toast by chunk-end (was Re: PG_PAGE_LAYOUT_VERSION 5 - time forchange)
Date: 2008-11-17 21:10:21
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Zdenek Kotala wrote:
> Alvaro Herrera napsal(a):
>> Heikki Linnakangas wrote:
>>> Hmm, you're right. I think it can be made to work by storing the 
>>> *end*  offset of each chunk. To find the chunk containing offset X, 
>>> search for  the first chunk with end_offset > X.
>> FWIW I'm trying to do this.  So far I've managed to make the basic thing
>> work, and I'm about to have a look at the slice interface.

Okay, so this seems to work.  It's missing writing the sanity checks on
the returned data, and a look at the SGML docs to see if anything needs
updating.  I'm also going to recheck code comments that may need

Alvaro Herrera                      
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

Attachment: toast-chunkend.patch
Description: text/x-diff (14.5 KB)

In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2008-11-17 21:27:53
Subject: Re: Compiling on HP-UX 10.20 fails
Previous:From: Aidan Van DykDate: 2008-11-17 20:40:41
Subject: Re: Block-level CRC checks

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group