Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 0069A47621C; Mon, 7 Oct 2002 11:22:09 -0400 (EDT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 520A5476720; Mon, 7 Oct 2002 11:21:58 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.5/8.12.5) with ESMTP id g97FLvhR023898; Mon, 7 Oct 2002 11:21:57 -0400 (EDT) To: shridhar_daithankar@persistent.co.in Cc: pgsql-hackers@postgresql.org, pgsql-general , pgsql-performance@postgresql.org Subject: Re: [pgsql-performance] Large databases, performance In-reply-to: <3DA1E50F.4394.107FF85D@localhost> References: <3DA1A331.21316.F7E742B@localhost> <3DA1E50F.4394.107FF85D@localhost> Comments: In-reply-to "Shridhar Daithankar" message dated "Mon, 07 Oct 2002 19:48:31 +0530" Date: Mon, 07 Oct 2002 11:21:57 -0400 Message-ID: <23897.1034004117@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200210/390 X-Sequence-Number: 31388 "Shridhar Daithankar" writes: > I say if it's a char field, there should be no indicator of length as > it's not required. Just store those many characters straight ahead.. Your assumption fails when considering UNICODE or other multibyte character encodings. regards, tom lane