Re: [HACKERS] Max tuple size.

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: darrenk(at)insightdist(dot)com (Darren King)
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Max tuple size.
Date: 1998-01-19 21:54:25
Message-ID: 199801192154.QAA00886@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
>
> This comes up since the varchar will no longer be padded...
>
> Should the user be allowed to create a table with fields that
> would go over the maximum tuple size if all fields were max'd?

Yes, text does not do checking, and certainly a table with three text
fields can go over the maximum.

>
> Example...with a block size of 8192...
>
> create table foo (a varchar(4000), b varchar(4000), c varchar(500));
>
> It's possible that a valid tuple according to the table definition
> will be rejected internally.
>
> 6.2 lets me create the above table, but won't let me insert in it
> unless at least one of the fields is null. 6.3 will allow the row
> as long as they collectively aren't more than the MAXTUPLEN.

IMHO, that is good.

> Should postgres issue a warning or an error about this condition
> when the table is created?

--
Bruce Momjian
maillist(at)candle(dot)pha(dot)pa(dot)us

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 1998-01-19 21:55:22 Re: [HACKERS] debug flag
Previous Message Shiby Thomas 1998-01-19 19:34:15 debug flag