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

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: 2007-01-30 14:51:16
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
"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

In response to


pgsql-hackers by date

Next:From: Magnus HaganderDate: 2007-01-30 14:58:40
Subject: Re: [BUGS] Missing error message on missing ssl-key-files
Previous:From: Magnus HaganderDate: 2007-01-30 14:40:55
Subject: Re: [HACKERS] Searching some sites explaing about PosgtreSQL

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