Re: [HACKERS] LONG varsize - how to go on

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Jan Wieck <wieck(at)debis(dot)com>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] LONG varsize - how to go on
Date: 1999-12-17 18:12:34
Message-ID: 199912171812.NAA20324@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> > >
> > > Christof Petig and me then could start implementing it, using
> > > lztext with locally disabled compression feature for the
> >
> > I would recommand having compression disabled by default, and enabled by
> > the user.
>
> Missed me here. I wanted to abuse lztext during development,
> having that only beeing considered for move off at all to get
> the in place tuple modification going. Then add all the other
> varsize types (there are 12 plus arrays currently) to have
> only one source of errors.

Oh, got it. You are going to implement long tuples for only the lztext
type at first. Excellent idea. Did you see someone on the general list
already is asking about long tuples for 7.0? I replied on our current
status.

--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jan Wieck 1999-12-17 19:26:36 Re: [HACKERS] LONG varsize - how to go on
Previous Message Bruce Momjian 1999-12-17 18:10:41 Re: [HACKERS] Re: Notation for nextval() (was Re: Several small patches)