Re: BUG #16405: Exception P0004 not caught in EXCEPTION WHEN OTHERS

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: jacobcrell(at)gmail(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16405: Exception P0004 not caught in EXCEPTION WHEN OTHERS
Date: 2020-04-30 17:04:25
Message-ID: 6966.1588266265@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> Excepted Behavior: P0004 exception is caught in EXCEPTION WHEN OTHERS,
> function returns text 'Hit the Other exception block'.
> Actual Behavior: P0004 exception is raised and remains uncaught.

That's intentional, per the documentation [1]:

The special condition name OTHERS matches every error type except
QUERY_CANCELED and ASSERT_FAILURE. (It is possible, but often unwise,
to trap those two error types by name.)

regards, tom lane

[1] https://www.postgresql.org/docs/current/plpgsql-control-structures.html#PLPGSQL-ERROR-TRAPPING

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Jacob Crell 2020-04-30 17:15:32 Re: BUG #16405: Exception P0004 not caught in EXCEPTION WHEN OTHERS
Previous Message Alex Movitz 2020-04-30 16:58:27 Re: BUG #16403: set_bit function does not have expected effect