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	Deduplicate "invalid input syntax" messages for various types.	2018-07-22 14:58:01 -07:00
input
output
sql	Indexes with INCLUDE columns and their support in B-tree	2018-04-07 23:00:39 +03:00
.gitignore
dblink--1.0--1.1.sql
dblink--1.1--1.2.sql
dblink--1.2.sql
dblink--unpackaged--1.0.sql
dblink.c	PG_FINALLY	2019-11-01 11:18:03 +01:00
dblink.control
Makefile	Prevent accidental linking of system-supplied copies of libpq.so etc.	2018-04-03 16:26:05 -04:00
pg_service.conf