pg.ddx.io pgsql-interfaces@postgresql.org mailing list archive
help / color / mirror / Atom feedpsql ERROR : Character Types Tuple is too big: size xxxxx
7+ messages / 4 participants
[nested] [flat]
* psql ERROR : Character Types Tuple is too big: size xxxxx
@ 2000-01-14 13:29 Compte utilisateur Sultan-advl <webmaster@advl.org>
0 siblings, 1 reply; 7+ messages in thread
From: Compte utilisateur Sultan-advl @ 2000-01-14 13:29 UTC (permalink / raw)
To: pgsql-interfaces; pgman@candle.pha.pa.us; pgsql-novice@postgresql.org; pgsql-general@postgresql.org; +Cc: jks@p1.selectacast.net; chalaoux@cybercable.fr
Hi,
From Bruce online book :
"There are synonyms for the terms table, row, and column. Table is more
formally referred to as a relation or class, row as record or tuple, and column
as field or attribute.
"
====
8Kb limit apply to :
'tuple' when insert ?
'tuple' in design stage (what's append with fixe types) ?
column (Case of fixe types) ???
What's wrong ?
- Design database
- Postgresql limit
Can't find informations on documentation and mail archive's obscure on 8Kb
limit.
Thanks fo help.
Emmanuel DISCORS
http://www.advl.org/kiwi/
===================
Error under psql interface :
A) The tuple in the 'insert' is < 8K but the tuple in table
description is > 8Kb
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 |
+----------------------------------+----------------------------------+-------+
Indices: localisation_pkey
localisationi1
localisationi2
localisationi3
B) The tuple in the 'insert' is < 8K and the tuple in table
description is < 8Kb
newkiwi=> insert into localisation values ('999', 'ee', 'ff', '999', 'gg', 'hh', 'ii', 'jj', '999');
INSERT 62016 1
newkiwi=> insert into localisation values ('999', 'ee', 'ff', '999', 'gg', 'hh', 'ii', 'jj', '999');
ERROR: Cannot insert a duplicate key into a unique index
newkiwi=> insert into localisation values ('9998', 'ee', 'ff', '999', 'gg', 'hh', 'ii', 'jj', '999');
INSERT 62018 1
newkiwi=> \d localisation
Table = localisation
+----------------------------------+----------------------------------+-------+
| Field | Type | Length|
+----------------------------------+----------------------------------+-------+
| id_loc | int4 not null | 4 |
| voie_loc | char() | 1024 |
| codebat_loc | char() | 1024 |
| idplan_loc | int4 | 4 |
| xplan_loc | char() | 1024 |
| yplan_loc | char() | 1024 |
| acces_loc | char() | 1024 |
| accesen_loc | char() | 1024 |
| id_ville_loc | int4 | 4 |
+----------------------------------+----------------------------------+-------+
Indices: localisation_pkey
localisationi1
localisationi2
localisationi3
===============================================
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: [INTERFACES] psql ERROR : Character Types Tuple is too big: size xxxxx
@ 2000-01-14 15:34 Tom Lane <tgl@sss.pgh.pa.us>
parent: Compte utilisateur Sultan-advl <webmaster@advl.org>
0 siblings, 1 reply; 7+ messages in thread
From: Tom Lane @ 2000-01-14 15:34 UTC (permalink / raw)
To: webmaster@advl.org; +Cc: pgsql-interfaces; pgsql-novice@postgreSQL.org; pgsql-general@postgreSQL.org
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
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: [NOVICE] Re: [INTERFACES] psql ERROR : Character Types Tuple is too big: size xxxxx
@ 2000-01-14 15:54 D. Duccini <duccini@backpack.com>
parent: Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 7+ messages in thread
From: D. Duccini @ 2000-01-14 15:54 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: webmaster@advl.org; pgsql-interfaces; pgsql-novice@postgreSQL.org; pgsql-general@postgreSQL.org
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!"
-----------------------------------------------------------------------------
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: [INTERFACES] psql ERROR : Character Types Tuple is too big: size xxxxx
@ 2000-01-14 18:00 Compte utilisateur Sultan-advl <webmaster@advl.org>
parent: D. Duccini <duccini@backpack.com>
0 siblings, 0 replies; 7+ messages in thread
From: Compte utilisateur Sultan-advl @ 2000-01-14 18:00 UTC (permalink / raw)
To: duccini@backpack.com; +Cc: pgsql-interfaces
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!"
> -----------------------------------------------------------------------------
^ permalink raw reply [nested|flat] 7+ messages in thread
* Fwd: Re: [INTERFACES] psql ERROR : Character Types Tuple is too big: size xxxxx
@ 2000-01-14 18:30 Compte utilisateur Sultan-advl <webmaster@advl.org>
0 siblings, 1 reply; 7+ messages in thread
From: Compte utilisateur Sultan-advl @ 2000-01-14 18:30 UTC (permalink / raw)
To: pgsql-interfaces
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
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: Fwd: Re: [INTERFACES] psql ERROR : Character Types Tuple is too big: size xxxxx
@ 2000-01-14 21:28 Tom Lane <tgl@sss.pgh.pa.us>
parent: Compte utilisateur Sultan-advl <webmaster@advl.org>
0 siblings, 1 reply; 7+ messages in thread
From: Tom Lane @ 2000-01-14 21:28 UTC (permalink / raw)
To: webmaster@advl.org; +Cc: pgsql-interfaces
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
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: Fwd: Re: [INTERFACES] psql ERROR : Character Types Tuple is too big: size xxxxx
@ 2000-01-27 03:21 Joseph Shraibman <jks@p1.selectacast.net>
parent: Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 7+ messages in thread
From: Joseph Shraibman @ 2000-01-27 03:21 UTC (permalink / raw)
To: pgsql-interfaces
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.
^ permalink raw reply [nested|flat] 7+ messages in thread
end of thread, other threads:[~2000-01-27 03:21 UTC | newest]
Thread overview: 7+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2000-01-14 13:29 psql ERROR : Character Types Tuple is too big: size xxxxx Compte utilisateur Sultan-advl <webmaster@advl.org>
2000-01-14 15:34 ` Tom Lane <tgl@sss.pgh.pa.us>
2000-01-14 15:54 ` D. Duccini <duccini@backpack.com>
2000-01-14 18:00 ` Compte utilisateur Sultan-advl <webmaster@advl.org>
2000-01-14 18:30 Fwd: Re: [INTERFACES] psql ERROR : Character Types Tuple is too big: size xxxxx Compte utilisateur Sultan-advl <webmaster@advl.org>
2000-01-14 21:28 ` Tom Lane <tgl@sss.pgh.pa.us>
2000-01-27 03:21 ` Joseph Shraibman <jks@p1.selectacast.net>
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