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

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

From
Compte utilisateur Sultan-advl
Date:
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@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


Compte utilisateur Sultan-advl <webmaster@advl.org> writes:
> [ tuple definition is bigger than 8K ]
> BUT why psql does not  raise an error in 'create table'  ?
> Maybe documentation needs more informations on this ? (In Data types)

Well, actually, we are more interested in getting rid of the limitation
than in adding more code that depends on it... there may even be a fix
in 7.0...
        regards, tom lane


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

From
Joseph Shraibman
Date:
Tom Lane wrote:

> Compte utilisateur Sultan-advl <webmaster@advl.org> writes:
> > [ tuple definition is bigger than 8K ]
> > BUT why psql does not  raise an error in 'create table'  ?
> > Maybe documentation needs more informations on this ? (In Data types)
>
> Well, actually, we are more interested in getting rid of the limitation
> than in adding more code that depends on it... there may even be a fix
> in 7.0...
>
>                         regards, tom lane
>
> ************

I found this in the hackers mailing list archive:

Bruce Momjian <pgman@candle.pha.pa.us>                at Technische
Universitaet Muenchen, Germany



Can I ask how our big open items for 7.0 are doing:
       Long tuples/TOAST(Jan)       Foriegn keys/action buffer(Jan)       Unify date/time types(Thomas)       Outer
Joins(Thomas)

I am only asking to know if we should continue with the planned Feb 1
beta?

====================END CLIP.

The problem is that none of the followups mentioned long tuples, so that
might have slipped through the cracks.