Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f4UKjdE68126 for ; Wed, 30 May 2001 16:45:39 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.3/8.11.3) with ESMTP id f4UKj9R04707; Wed, 30 May 2001 16:45:09 -0400 (EDT) To: Mark cc: pgsql-sql@postgresql.org Subject: Re: Case Insensitive Queries In-reply-to: <200105301857.f4UIvoW17610@mail.ldssingles.com> References: <200105301549.f4UFnfW16237@mail.ldssingles.com> <24650.991241602@sss.pgh.pa.us> <200105301857.f4UIvoW17610@mail.ldssingles.com> Comments: In-reply-to Mark message dated "30 May 2001 12:06:00 -0600" Date: Wed, 30 May 2001 16:45:09 -0400 Message-ID: <4704.991255509@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200105/346 X-Sequence-Number: 3187 Mark writes: > Even the postgresql documentation asserts something similar to this: You're reading obsolete documentation. There is no such assertion (as far as I can find, anyway) in the 7.1 documentation. The speed advantage of bpchar --- which was always extremely marginal anyway, if it was real at all when you consider I/O costs --- is gone completely now, because with TOAST in the picture the system cannot assume that bpchar is fixed length on disk. regards, tom lane