Re: stack usage in toast_insert_or_update() - Mailing list pgsql-hackers

From Tom Lane
Subject Re: stack usage in toast_insert_or_update()
Date
Msg-id 16858.1170226124@sss.pgh.pa.us
Whole thread Raw
In response to Re: stack usage in toast_insert_or_update()  ("Pavan Deolasee" <pavan.deolasee@gmail.com>)
Responses Re: stack usage in toast_insert_or_update()  ("Pavan Deolasee" <pavan.deolasee@gmail.com>)
List pgsql-hackers
"Pavan Deolasee" <pavan.deolasee@gmail.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


pgsql-hackers by date:

Previous
From: "Pavan Deolasee"
Date:
Subject: Re: stack usage in toast_insert_or_update()
Next
From: imad
Date:
Subject: Re: PL/pgSQL RENAME functionality in TODOs