Received: from sultan.intranet.org (root@ppp-100-50.infonie.fr [195.242.100.50]) by hub.org (8.9.3/8.9.3) with ESMTP id NAA48767 for ; Fri, 14 Jan 2000 13:29:21 -0500 (EST) (envelope-from advl@advl.org) Received: from localhost (localhost [[UNIX: localhost]]) by sultan.intranet.org (8.9.3/8.9.3) id TAA01963; Fri, 14 Jan 2000 19:04:41 +0100 From: Compte utilisateur Sultan-advl Reply-To: webmaster@advl.org Organization: ADVL To: Subject: Re: [INTERFACES] psql ERROR : Character Types Tuple is too big: size xxxxx Date: Fri, 14 Jan 2000 19:00:08 +0100 X-Mailer: KMail [version 1.0.21] Content-Type: text/plain Cc: pgsql-interfaces@postgreSQL.org References: MIME-Version: 1.0 Message-Id: <00011419044100.01934@sultan> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.org id NAA49326 Hi, Just to see if psql raise an error message ;-) Emmanuel. Le ven, 14 jan 2000, D. Duccini a écrit : > and on top of that, why insert character strings into columns expecting > numeric values? > > defintely use VARCHAR unless you are going to be filling those columns up > > -duck > > > 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 > > > > ************ > > > > > ----------------------------------------------------------------------------- > david@backpack.com BackPack Software, Inc. www.backpack.com > +1 651.645.7550 voice "Life is an Adventure. > +1 651.645.9798 fax Don't forget your BackPack!" > -----------------------------------------------------------------------------