On 1/31/07, Tom Lane <[EMAIL PROTECTED]> wrote:
We can't change TOAST_MAX_CHUNK_SIZE without forcing an initdb, but I think that it would be safe to remove the MAXALIGN'ing of the tuple size in the tests in heapam.c, that is
That would mean that the tuple size in the heap may exceed TOAST_TUPLE_THRESHOLD which should be OK, but we may want to have a comment explaining that. We should do the same for heap_update() as well. Thanks, Pavan -- EnterpriseDB http://www.enterprisedb.com
