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
to allocate only as much space as required ?
pgsql-hackers by date
|Next:||From: Guido Goldstein||Date: 2007-01-30 10:43:52|
|Subject: Re: pgsql: Fix for plpython functions; return true/false for boolean,|
|Previous:||From: Ken Johanson||Date: 2007-01-30 06:53:51|
|Subject: V3 protocol; way to return table aliases?|