How to know if SPI or some other API triggered an ERROR. - Mailing list pgsql-general

From dandl
Subject How to know if SPI or some other API triggered an ERROR.
Date
Msg-id 000001d1b34d$5b50f120$11f2d360$@andl.org
Whole thread Raw
Responses Re: How to know if SPI or some other API triggered an ERROR.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general

The question is whether there is any way to know that some Postgres API call such as SPI (or others) did not return but instead triggered an elog(ERROR).

 

The context is the implementation of a language handler (plandl for Andl) with the possibility of re-entrant calls to functions. I would like to be able to recover from Postgres errors, but that’s quite difficult if I don’t know that one has happened, particularly if it happens inside a nested call that needs to be unwound.

 

Any suggestions appreciated.

 

Regards

David M Bennett FACS


Andl - A New Database Language - andl.org

 

pgsql-general by date:

Previous
From: Chris Travers
Date:
Subject: Re: Thoughts on "Love Your Database"
Next
From: Szymon Lipiński
Date:
Subject: Re: Thoughts on "Love Your Database"