Sender: jks@p1.selectacast.net
Message-ID: <388FB9D5.2B97A155@selectacast.net>
Date: Wed, 26 Jan 2000 22:21:57 -0500
From: Joseph Shraibman <jks@p1.selectacast.net>
Organization: Xtenit
MIME-Version: 1.0
To: pgsql-interfaces@postgresql.org
Subject: Re: Fwd: Re: [INTERFACES] psql ERROR : Character Types Tuple is too
	big: size xxxxx
References: <00011419312100.02025@sultan> <1162.947885334@sss.pgh.pa.us>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

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.