Skip site navigation (1) Skip section navigation (2)

stack usage in toast_insert_or_update()

From: "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: stack usage in toast_insert_or_update()
Date: 2007-01-30 10:17:59
Message-ID: 2e78013d0701300217v1a303199s5195547f518007c6@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
Not sure whether its worth optimizing, but had spotted this while browsing
the code a while back. So thought would post it anyways.

The stack usage for toast_insert_or_update() may run into several KBs since
the MaxHeapAttributeNumber is set to a very large value of 1600. The usage
could anywhere between 28K to 48K depending on alignment and whether its a
32-bit or a 64-bit machine.

Is it very common to have so many attributes in a table ? If not, would it
be worth
to allocate only as much space as required ?

Thanks,
Pavan

-- 

EnterpriseDB     http://www.enterprisedb.com

Responses

pgsql-hackers by date

Next:From: Guido GoldsteinDate: 2007-01-30 10:43:52
Subject: Re: pgsql: Fix for plpython functions; return true/false for boolean,
Previous:From: Ken JohansonDate: 2007-01-30 06:53:51
Subject: V3 protocol; way to return table aliases?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group