Fwd: Re: [INTERFACES] psql ERROR : Character Types Tuple is too big: size xxxxx

From: Compte utilisateur Sultan-advl <webmaster(at)advl(dot)org>
To: pgsql-interfaces(at)postgresql(dot)org
Subject: Fwd: Re: [INTERFACES] psql ERROR : Character Types Tuple is too big: size xxxxx
Date: 2000-01-14 18:30:00
Message-ID: 00011419312100.02025@sultan
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-interfaces

Thanks Tom,
Taking the choice of 'text' fields ; "no needs of blank-padding in every
record..."
BUT why psql does not raise an error in 'create table' ?
Maybe documentation needs more informations on this ? (In Data types)
Emmanuel.

Le ven, 14 jan 2000, vous avez crit :
> Compte utilisateur Sultan-advl <webmaster(at)advl(dot)org> writes:
> > newkiwi=> insert into localisation values ('999', 'ee', 'ff', '999', 'gg',
> > 'hh', 'ii', 'jj', '999');
> > ERROR: Tuple is too big: size 12356
> > newkiwi=> \d localisation
> > Table = localisation
> > +----------------------------------+----------------------------------+-------+
> > | Field | Type | Length|
> > +----------------------------------+----------------------------------+-------+
> > | id_loc | int4 not null | 4 |
> > | voie_loc | char() | 2048 |
> > | codebat_loc | char() | 2048 |
> > | idplan_loc | int4 | 4 |
> > | xplan_loc | char() | 2048 |
> > | yplan_loc | char() | 2048 |
> > | acces_loc | char() | 2048 |
> > | accesen_loc | char() | 2048 |
> > | id_ville_loc | int4 | 4 |
> > +----------------------------------+----------------------------------+-------+
>
> Well, you've got six fixed-size 2K fields, which are going to take up
> 12K all by themselves, plus there's a few dozen bytes of overhead.
>
> I'd suggest using varchar or text instead of char --- do you really
> need 12K of blank-padding in every record?
>
> regards, tom lane

Responses

Browse pgsql-interfaces by date

  From Date Subject
Next Message Michael Meskes 2000-01-14 20:46:03 Re: [INTERFACES] Setup of PGAdmin
Previous Message Constantin Teodorescu 2000-01-14 18:16:44 Re: [INTERFACES] PgAccess