From: Martijn van Oosterhout <kleptog@svana.org>
To: Shridhar Daithankar <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: Tue, 8 Oct 2002 17:20:47 +1000
Message-ID: <20021008072047.GB558@svana.org> (raw)
In-Reply-To: <3DA2BE03.3674.13CF7DD1@localhost>
References: <3DA1E50F.4394.107FF85D@localhost>
<3DA2BE03.3674.13CF7DD1@localhost>
On Tue, Oct 08, 2002 at 11:14:11AM +0530, Shridhar Daithankar wrote:
> On 7 Oct 2002 at 11:21, Tom Lane wrote:
>
> > "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.
>
> Correct but is it possible to have real char string when database is not
> unicode or when locale defines size of char, to be exact?
>
> In my case varchar does not make sense as all strings are guaranteed to be of
> defined length. While the argument you have put is correct, it's causing a disk
> space leak, to say so.
Well, maybe. But since 7.1 or so char() and varchar() simply became text
with some length restrictions. This was one of the reasons. It also
simplified a lot of code.
--
Martijn van Oosterhout <kleptog@svana.org> http://svana.org/kleptog/> There are 10 kinds of people in the world, those that can do binary
> arithmetic and those that can't.
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: kleptog@svana.org, shridhar_daithankar@persistent.co.in, pgsql-general@postgresql.org, pgsql-performance@postgresql.org
Subject: Re: [pgsql-performance] Large databases, performance
In-Reply-To: <20021008072047.GB558@svana.org>
* 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