From 604bd3671121b51f977de146ed95484c2297fb3e Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Fri, 1 Nov 2019 11:09:52 +0100 Subject: 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 --- contrib/sepgsql/hooks.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) (limited to 'contrib/sepgsql/hooks.c') diff --git a/contrib/sepgsql/hooks.c b/contrib/sepgsql/hooks.c index 992c70e8a06..49f32ac4d33 100644 --- a/contrib/sepgsql/hooks.c +++ b/contrib/sepgsql/hooks.c @@ -372,13 +372,11 @@ sepgsql_utility_command(PlannedStmt *pstmt, context, params, queryEnv, dest, completionTag); } - PG_CATCH(); + PG_FINALLY(); { sepgsql_context_info = saved_context_info; - PG_RE_THROW(); } PG_END_TRY(); - sepgsql_context_info = saved_context_info; } /* -- cgit v1.2.3