| From: | "Ansley, Michael" <Michael(dot)Ansley(at)intec(dot)co(dot)za> |
|---|---|
| To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | RE: [HACKERS] Token length limit |
| Date: | 1999-08-13 14:21:00 |
| Message-ID: | 1BF7C7482189D211B03F00805F8527F70ED0E1@S-NATH-EXCH2 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>> (Actually I think the limit is currently 64k not 16k, because of the
>> hack that parser/Makefile applies to scan.c, but the point is there
>> shouldn't be any hardwired limit...)
Yes, I noticed that hack.
>> Yes, and yes. It's not a critical issue as long as we have limited
>> tuple sizes, but we do need to fix this eventually.
The theory is, of course, that now the query string lengths are unlimited,
there is good reason to remove the tuple block-size limit. Somebody...
somebody.... anybody.....
Anyway, it has been a good learning experience, and thanks for everybody's
help so far. With some luck, the debugging process will be short and sweet.
MikeA
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 1999-08-13 14:33:49 | Re: [HACKERS] Index scan? |
| Previous Message | Tom Lane | 1999-08-13 14:13:43 | Re: [HACKERS] Token length limit |