postgresql/contrib/hstore_plpython
Peter Eisentraut 604bd36711 PG_FINALLY
This gives an alternative way of catching exceptions, for the common
case where the cleanup code is the same in the error and non-error
cases.  So instead of

    PG_TRY();
    {
        ... code that might throw ereport(ERROR) ...
    }
    PG_CATCH();
    {
        cleanup();
	PG_RE_THROW();
    }
    PG_END_TRY();
    cleanup();

one can write

    PG_TRY();
    {
        ... code that might throw ereport(ERROR) ...
    }
    PG_FINALLY();
    {
        cleanup();
    }
    PG_END_TRY();

Discussion: https://www.postgresql.org/message-id/flat/95a822c3-728b-af0e-d7e5-71890507ae0c%402ndquadrant.com
2019-11-01 11:18:03 +01:00
..
expected
sql
.gitignore
hstore_plpython2u--1.0.sql
hstore_plpython2u.control
hstore_plpython3u--1.0.sql
hstore_plpython3u.control
hstore_plpython.c PG_FINALLY 2019-11-01 11:18:03 +01:00
hstore_plpythonu--1.0.sql
hstore_plpythonu.control
Makefile Fix out-of-tree build for transform modules. 2018-09-16 18:46:45 +01:00