| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Jan Wieck <wieck(at)debis(dot)com>, PostgreSQL HACKERS <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: [HACKERS] LONG vs. Toaster |
| Date: | 1999-12-21 04:57:34 |
| Message-ID: | 6393.945752254@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>> This might interfere with the LZTEXT data type as is. Since
>> this new data type isn't released yet, I'll have to remove it
>> again before freeze. The compressor/decompressor will become
>> part of the toaster.
>>
>> Needs to revert the changes to pg_rewrite too, so the next
>> release will NOT gain any bigger rules. But to release it and
>> later fight problems that I already see, only to enable
>> bigger rules right now, is IMHO the wrong decision.
> Agreed.
Yes. I thought that LZTEXT was redundant as soon as we agreed that
compression could be part of the out-of-line storage mechanism.
Better to pull it now than have to support it long after it has
no purpose. We can struggle along with limited-length rules for
a little bit longer.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 1999-12-21 05:07:07 | Re: [HACKERS] SPI Headers -- RPM distribution |
| Previous Message | Tom Lane | 1999-12-21 04:53:42 | Re: [HACKERS] T-O-A-S-T meaning |