Re: [HACKERS] varchar size

From: darrenk(at)insightdist(dot)com (Darren King)
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] varchar size
Date: 1998-01-08 16:31:10
Message-ID: 9801081631.AA89094@ceodev
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> I have applied the following patch to allow varchar() fields to store
> just the needed bytes, and not the maximum size.
>
> ...
>
> And if I create a varchar(2000), it does not take several 8k blocks to
> store 10 rows, like it did before.

Fixes the following "problem" too...

Currently, you can create a table with attributes that _can_ total more
than the max_tup_size if they maximum size, but not be able to insert
valid data into all of them.

For instance, ...

create table foo (bar varchar(4000),
bah varchar(3000),
baz varchar(2000));

... is fine as long as one of the attributes is null. Now you can have
non-null values for all three as long as they don't go over max_tup_size
in _total_.

darrenk

Browse pgsql-hackers by date

  From Date Subject
Next Message Darren King 1998-01-08 17:02:40 Disk block size issues.
Previous Message The Hermit Hacker 1998-01-08 15:01:18 Re: [HACKERS] Did the patch get recieved?