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 --- src/backend/commands/trigger.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) (limited to 'src/backend/commands/trigger.c') diff --git a/src/backend/commands/trigger.c b/src/backend/commands/trigger.c index 7ba859d446d..0b84de59437 100644 --- a/src/backend/commands/trigger.c +++ b/src/backend/commands/trigger.c @@ -2431,13 +2431,11 @@ ExecCallTriggerFunc(TriggerData *trigdata, { result = FunctionCallInvoke(fcinfo); } - PG_CATCH(); + PG_FINALLY(); { MyTriggerDepth--; - PG_RE_THROW(); } PG_END_TRY(); - MyTriggerDepth--; pgstat_end_function_usage(&fcusage, true); -- cgit v1.2.3