From: Tom Lane <tgl@sss.pgh.pa.us>
To: shridhar_daithankar@persistent.co.in
Cc: pgsql-hackers@postgresql.org, pgsql-general <pgsql-general@postgresql.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: [pgsql-performance] Large databases, performance
Date: Mon, 07 Oct 2002 11:21:57 -0400
Message-ID: <23897.1034004117@sss.pgh.pa.us> (raw)
In-Reply-To: <3DA1E50F.4394.107FF85D@localhost>
References: <3DA1A331.21316.F7E742B@localhost>
<3DA1E50F.4394.107FF85D@localhost>
"Shridhar Daithankar" <shridhar_daithankar@persistent.co.in> writes:
> I say if it's a char field, there should be no indicator of length as
> it's not required. Just store those many characters straight ahead..
Your assumption fails when considering UNICODE or other multibyte
character encodings.
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, shridhar_daithankar@persistent.co.in, pgsql-general@postgresql.org, pgsql-performance@postgresql.org
Subject: Re: [pgsql-performance] Large databases, performance
In-Reply-To: <23897.1034004117@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