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

From dandl
Subject Re: How to know if SPI or some other API triggered an ERROR.
Date
Msg-id 002201d1b3c9$b88a12f0$299e38d0$@andl.org
Whole thread Raw
In response to Re: How to know if SPI or some other API triggered an ERROR.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Thanks. Yes, I have seen those around and kind of wondered.

It looks like it can only be used in a "C" context. Should do what I need,
if I can find the right place to put it.

Regards
David M Bennett FACS

Andl - A New Database Language - andl.org



> -----Original Message-----
> From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
> Sent: Sunday, 22 May 2016 12:01 AM
> To: dandl <david@andl.org>
> Cc: 'PostgreSQL' <pgsql-general@postgresql.org>
> Subject: Re: [GENERAL] How to know if SPI or some other API triggered an
> ERROR.
>
> "dandl" <david@andl.org> writes:
> > 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).
>
> I think what you're looking for is to set up a PG_TRY/PG_CATCH block to
> intercept the error as the stack is being unwound.
>
>             regards, tom lane



pgsql-general by date:

Previous
From: John R Pierce
Date:
Subject: Re: PostgreSql Doubt
Next
From: Tory M Blue
Date:
Subject: 9.5 CentOS 7 setting PGDATA for systemctl