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: Wed, 31 Jan 2007 01:48:44 -0500
"Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com> writes: > Btw, I noticed that the toast_insert_or_update() is re-entrant. > toast_save_datum() calls simple_heap_insert() which somewhere down the > line calls toast_insert_or_update() again. The toast code takes pains to ensure that the tuples it creates won't be subject to re-toasting. Else it'd be an infinite recursion. 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
- Re: stack usage in toast_insert_or_update()
- From: Tom Lane
- Re: stack usage in toast_insert_or_update()
- From: Pavan Deolasee
- stack usage in toast_insert_or_update()
- Prev by Date: Re: stack usage in toast_insert_or_update()
- Next by Date: Re: PL/pgSQL RENAME functionality in TODOs
- Previous by thread: Re: stack usage in toast_insert_or_update()
- Next by thread: Re: stack usage in toast_insert_or_update()
- Indexes: