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

From Pavan Deolasee
Subject stack usage in toast_insert_or_update()
Date
Msg-id 2e78013d0701300217v1a303199s5195547f518007c6@mail.gmail.com
Whole thread Raw
Responses Re: stack usage in toast_insert_or_update()
List pgsql-hackers
<br clear="all" />Not sure whether its worth optimizing, but had spotted this while browsing<br />the code a while
back.So thought would post it anyways.<br /><br />The stack usage for toast_insert_or_update() may run into several KBs
since<br />the MaxHeapAttributeNumber is set to a very large value of 1600. The usage<br />could anywhere between 28K
to48K depending on alignment and whether its a<br />32-bit or a 64-bit machine.<br /><br />Is it very common to have so
manyattributes in a table ? If not, would it be worth <br />to allocate only as much space as required ?<br /><br
/>Thanks,<br/>Pavan<br /><br />-- <br /><br />EnterpriseDB     <a
href="http://www.enterprisedb.com">http://www.enterprisedb.com</a>

pgsql-hackers by date:

Previous
From: Ken Johanson
Date:
Subject: V3 protocol; way to return table aliases?
Next
From: Gregory Stark
Date:
Subject: Bug? CREATE TABLE AS (... UNION ...)