pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Compte utilisateur Sultan-advl <webmaster@advl.org>
To: duccini@backpack.com
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] psql ERROR : Character Types Tuple is too big: size xxxxx
Date: Fri, 14 Jan 2000 19:00:08 +0100
Message-ID: <00011419044100.01934@sultan> (raw)
References: <Pine.GSO.3.96.1000114095253.23313B-100000@ra.bpsi.net>

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 <webmaster@advl.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
> > 
> > ************
> > 
> 
> 
> -----------------------------------------------------------------------------
> 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!"   
> -----------------------------------------------------------------------------



view thread (7+ messages)  latest in thread

Message-ID: <00011419044100.01934@sultan>
Permalink:  ../00011419044100.01934@sultan/
Also on:    postgresql.org/message-id/00011419044100.01934@sultan

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-interfaces@postgresql.org
  Cc: webmaster@advl.org, duccini@backpack.com
  Subject: Re: [INTERFACES] psql ERROR : Character Types Tuple is too big: size xxxxx
  In-Reply-To: <00011419044100.01934@sultan>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox