Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id KAA06124; Fri, 14 Jan 2000 10:34:19 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id KAA29534; Fri, 14 Jan 2000 10:34:14 -0500 (EST) To: webmaster@advl.org cc: pgsql-interfaces@postgreSQL.org, pgsql-novice@postgreSQL.org, pgsql-general@postgreSQL.org Subject: Re: [INTERFACES] psql ERROR : Character Types Tuple is too big: size xxxxx In-reply-to: <00011415015800.01007@sultan> References: <00011415015800.01007@sultan> Comments: In-reply-to Compte utilisateur Sultan-advl message dated "Fri, 14 Jan 2000 14:29:34 +0100" Date: Fri, 14 Jan 2000 10:34:14 -0500 Message-ID: <29531.947864054@sss.pgh.pa.us> From: Tom Lane 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