Postgres Pro
Downloads
Home   >   mailing lists

Re: stack usage in toast_insert_or_update() - Mailing list pgsql-hackers

From Pavan Deolasee
Subject Re: stack usage in toast_insert_or_update()
Date
Msg-id 2e78013d0702010344n56a560abn577e9d85669f35f1@mail.gmail.com
Whole thread Raw
In response to Re: stack usage in toast_insert_or_update()  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view

On 1/31/07, Tom Lane <tgl@sss.pgh.pa.us> 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

pgsql-hackers by date:

Previous
From: "Simon Riggs"
Date:
Subject: Re: max_locks_per_transactions ...
Next
From: "Simon Riggs"
Date:
Subject: Re: Improving NOT IN