| From: | Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> |
|---|---|
| To: | martin(dot)chantler(at)convergys(dot)com |
| Cc: | mpm(at)norwottuck(dot)com, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: tuples too big |
| Date: | 2001-02-08 15:30:37 |
| Message-ID: | 3A82BB9D.95D8210B@wgcr.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
martin(dot)chantler(at)convergys(dot)com wrote:
> This works well for things like notes and memo's but probably not so good
> for
> huge amounts of data. Its flexible and there's no hardcoded limit to the
> length of data.
Sounds something like TOAST, part of PostgreSQL 7.1, to be released
soon. TOAST, however, is in the backend itself and is fully automatic.
Hardcoded row limits on the amount of data per row (there is still a
limit on the number of _columns_ in a row, but not on the size of each
column) are gone in 7.1.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gunnar R|nning | 2001-02-08 15:36:24 | Re: full text searching |
| Previous Message | Brice Ruth | 2001-02-08 15:25:49 | Re: monitoring running queries? |