Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id D1577476950 for ; Tue, 8 Oct 2002 10:41:19 -0400 (EDT) Received: from www.pspl.co.in (www.pspl.co.in [202.54.11.65]) by postgresql.org (Postfix) with ESMTP id B1881476992 for ; Tue, 8 Oct 2002 10:41:14 -0400 (EDT) Received: (from root@localhost) by www.pspl.co.in (8.11.6/8.11.6) id g98EgrE13773 for ; Tue, 8 Oct 2002 20:12:53 +0530 Received: from daithan (daithan.intranet.pspl.co.in [192.168.7.161]) by www.pspl.co.in (8.11.6/8.11.0) with ESMTP id g98Egrv13768 for ; Tue, 8 Oct 2002 20:12:53 +0530 From: "Shridhar Daithankar" To: pgsql-performance@postgresql.org Date: Tue, 08 Oct 2002 20:11:47 +0530 MIME-Version: 1.0 Subject: Re: [GENERAL] Large databases, performance Reply-To: shridhar_daithankar@persistent.co.in Message-ID: <3DA33C03.31407.15BBAE9C@localhost> References: <1034085052.1094.14.camel@haggis> In-reply-to: <1928.1034087882@sss.pgh.pa.us> X-mailer: Pegasus Mail for Windows (v4.02) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200210/61 X-Sequence-Number: 78 On 8 Oct 2002 at 10:38, Tom Lane wrote: > Ron Johnson writes: > It's not simpler: it's more complicated, because you need an additional > input item to figure out the size of any given column in a record. > Making sure that that info is available every place it's needed is one > of the costs of supporting a feature like this. I understand. Can we put this in say page header instead of tuple header. While all the arguments you have put are really good, the stellar redundancy certainly can do with a mid-way solution. Just a thought.. Bye Shridhar -- bit, n: A unit of measure applied to color. Twenty-four-bit color refers to expensive $3 color as opposed to the cheaper 25 cent, or two-bit, color that use to be available a few years ago.