Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: stack usage in toast_insert_or_update()
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com>
- Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
- Subject: Re: stack usage in toast_insert_or_update()
- Date: Tue, 30 Jan 2007 09:51:16 -0500
"Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com> writes: > 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. So? The routine is not re-entrant so I don't see that the stack space is a big problem. It's coded that way to avoid palloc/pfree cycles... regards, tom lane
- Follow-Ups:
- Re: stack usage in toast_insert_or_update()
- From: Pavan Deolasee
- Re: stack usage in toast_insert_or_update()
- References:
- stack usage in toast_insert_or_update()
- From: Pavan Deolasee
- stack usage in toast_insert_or_update()
- Prev by Date: Re: pgsql: Fix for plpython functions; return true/false for boolean,
- Next by Date: Re: [BUGS] Missing error message on missing ssl-key-files
- Previous by thread: stack usage in toast_insert_or_update()
- Next by thread: Re: stack usage in toast_insert_or_update()
- Indexes: