Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [206.210.65.6]) by hub.org (8.9.3/8.9.3) with ESMTP id NAA24451 for ; Sat, 12 Jun 1999 13:01:19 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id NAA15519; Sat, 12 Jun 1999 13:00:41 -0400 (EDT) To: Alexander Schneider cc: pgsql-sql@postgreSQL.org Subject: Re: [SQL] Full-Text-Indexing In-reply-to: Your message of Sat, 12 Jun 1999 10:11:31 +0200 <1282947191-50950897@mail.isolution.de> Date: Sat, 12 Jun 1999 13:00:41 -0400 Message-ID: <15517.929206841@sss.pgh.pa.us> From: Tom Lane Alexander Schneider writes: > 1) Why should I use "varchar(n)" instead of "text" though the space for a > varchar-field is larger than text (varchar: 4byte+n, text: 2byte+n)? Is > it more efficient for queries? Actually, both text and varchar have 4-byte overhead. There's no difference at all in the representation, and none to speak of in efficiency. The reason you'd use varchar() is if you have an application-defined restriction that the contents of the field may not exceed some particular length. In that case you say varchar(N), which both makes the intent visible and allows Postgres to enforce the requirement for you. If you don't have any particular upper bound in mind for the string length, use text type. Just for completeness: char(N) also has a 4-byte overhead ... rather unnecessarily, but that's how it's done at the moment. But there is a marginal (very marginal) efficiency gain in access, since the system knows that the field is always the same length --- that makes it easier to determine the locations of following fields in the same tuple. I think you'd pretty much only use char(N) when you have an application semantics restriction that the string length must be exactly N characters. For example, in US postal addresses the state abbreviation would be char(2). regards, tom lane