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 01BF9D1D2AC for ; Sat, 6 Mar 2004 04:21:08 +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 58358-03 for ; Sat, 6 Mar 2004 00:21:10 -0400 (AST) Received: from relay01.kbs.net.au (relay01.kbs.net.au [203.220.32.149]) by svr1.postgresql.org (Postfix) with ESMTP id 66D40D1D25D for ; Sat, 6 Mar 2004 00:21:05 -0400 (AST) Received: from [203.221.247.164] (helo=familyhealth.com.au) by relay01.kbs.net.au with esmtp (Exim 3.36 #2) id 1AzTId-0007P9-00; Sat, 06 Mar 2004 15:20:32 +1100 Message-ID: <4049518D.70705@familyhealth.com.au> Date: Sat, 06 Mar 2004 12:20:29 +0800 From: Christopher Kings-Lynne User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031205 Thunderbird/0.4 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Rod Taylor Cc: Mike Nolan , Josh Berkus , Bill Moran , Jeff , Postgresql Performance Subject: Re: Fixed width rows faster? References: <200403052343.i25NhYsv021796@gw.tssi.com> <1078530843.57624.24.camel@jester> In-Reply-To: <1078530843.57624.24.camel@jester> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/67 X-Sequence-Number: 5923 >>You don't consider a requirement that a field be no longer than a >>certain length a reason not to use TEXT? Can't you just create a TEXT(255) field same as you can just create VARCHAR (with no length) field? I think they're basically synonyms for each other these days. Chris