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-31 06:48:44
Message-ID: 16858.1170226124@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
"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

In response to

Responses

pgsql-hackers by date

Next:From: imadDate: 2007-01-31 07:15:40
Subject: Re: PL/pgSQL RENAME functionality in TODOs
Previous:From: Pavan DeolaseeDate: 2007-01-31 05:48:30
Subject: Re: stack usage in toast_insert_or_update()

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