From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mark <mark@zserve.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Case Insensitive Queries
Date: Wed, 30 May 2001 16:45:09 -0400
Message-ID: <4704.991255509@sss.pgh.pa.us> (raw)
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>
Mark <mark@zserve.com> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, mark@zserve.com
Subject: Re: Case Insensitive Queries
In-Reply-To: <4704.991255509@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox