Received: from sultan.intranet.org (root@ppp2-17-168.infonie.fr [212.232.17.168]) by hub.org (8.9.3/8.9.3) with ESMTP id NAA47876 for ; Fri, 14 Jan 2000 13:21:49 -0500 (EST) (envelope-from advl@advl.org) Received: from localhost (localhost [[UNIX: localhost]]) by sultan.intranet.org (8.9.3/8.9.3) id TAA02049 for pgsql-interfaces@postgresql.org; Fri, 14 Jan 2000 19:31:21 +0100 From: Compte utilisateur Sultan-advl Reply-To: webmaster@advl.org Organization: ADVL To: pgsql-interfaces@postgresql.org Subject: Fwd: Re: [INTERFACES] psql ERROR : Character Types Tuple is too big: size xxxxx Date: Fri, 14 Jan 2000 19:30:00 +0100 X-Mailer: KMail [version 1.0.21] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <00011419312100.02025@sultan> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.org id NAA47915 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 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