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 20:37:55 |
Message-ID: | 199912172037.PAA01074@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Bruce Momjian wrote:
>
> > 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.
>
> I've seen several such questions these days. And I fear, if
> I'm not able to get at least the required catalog changes
> into 7.0, I'd have to wait until after 7.0 freeze + CVS
> branch before I can start at all. That'd cost us too much
> time.
>
> I know that I can deal with a bunch of deferred patches,
> staying in sync with CURRENT and having new features only as
> patches. But that worx only as long as I have most catalog
> changes in CURRENT. One single concurrent catalog change can
> cost me days of work in the worst case otherwise.
The Feb 1 date is not set in stone. If you would prefer March 1, we can
look at that option.
I pushed for an earlier release because I didn't want to wait for _all_
open items to be completed before a release.
--
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
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 1999-12-17 21:14:05 | Re: [HACKERS] LONG varsize - how to go on |
Previous Message | Jan Wieck | 1999-12-17 19:26:36 | Re: [HACKERS] LONG varsize - how to go on |