X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 7333ED1D43B for ; Sat, 6 Mar 2004 20:52:30 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 14042-10 for ; Sat, 6 Mar 2004 16:52:30 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 6AC39D1D306 for ; Sat, 6 Mar 2004 16:52:28 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i26KqQZs018297; Sat, 6 Mar 2004 15:52:27 -0500 (EST) To: "Eric Jain" Cc: "pgsql-performance" Subject: Re: Fixed width rows faster? In-reply-to: <004501c4037d$63e27f80$c300000a@caliente> References: <404889A6.7@potentialtech.com> <200403051528.55578.josh@agliodbs.com> <004501c4037d$63e27f80$c300000a@caliente> Comments: In-reply-to "Eric Jain" message dated "Sat, 06 Mar 2004 14:17:35 +0100" Date: Sat, 06 Mar 2004 15:52:26 -0500 Message-ID: <18296.1078606346@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/75 X-Sequence-Number: 5931 "Eric Jain" writes: > The main reason why I am still using VARCHAR rather than TEXT in many > places is to ensure that the column can be indexed. Postgres, it seems, > refuses to insert a string that is longer than some value into an > indexed column, and I'll rather have such errors flagged while inserting > a row rather than while rebuilding an index after having inserted lots > of rows. This is bogus reasoning. The limit on index entry length will not change when you rebuild the index. regards, tom lane