Re: Trapping PL/Perl spi_query_exec errors - Mailing list pgsql-general

From Greg Sabino Mullane
Subject Re: Trapping PL/Perl spi_query_exec errors
Date
Msg-id f5cb3c0b21efa6f2212128cf8cbde930@biglumber.com
Whole thread Raw
In response to Re: Trapping PL/Perl spi_query_exec errors  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


"Worky Workerson" <worky.workerson@gmail.com> wrote:
> This is probably a really basic question, but how do I trap when
> spi_query_exec returns an error in PL/Perl?

Tom Lane replied:
> I think you don't, without using plperlu :-(.  Unless perhaps recent
> Perls have added an error trapping construct that's separate from eval?

Tom is right, you need plperlu if you want to do this. Or be more careful
in your function by (for example) querying the pg_class table to see if
the table exists. Another alternative is to have pl/perlu do all the
"heavy lifting", and make some more limited wrapper functions in pl/perl.
And for the sake of the archives, it is "spi_exec_query" not "spi_query_exec".

- --
Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 200611230659
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8


-----BEGIN PGP SIGNATURE-----

iD8DBQFFZY2yvJuQZxSWSsgRAid1AKCBbLpjAYK/MMpQPiDBKapoOAIqygCfTrme
pDZrkflT0LLUvdlbWDxCoe0=
=OT2k
-----END PGP SIGNATURE-----



pgsql-general by date:

Previous
From: Arnaud Lesauvage
Date:
Subject: Re: URL Decoding
Next
From: "Brendan Jurd"
Date:
Subject: Re: ISO week dates