From: Tom Lane <tgl@sss.pgh.pa.us>
To: soumik.bhattacharjee@kpn.com
cc: pgsql-admin@lists.postgresql.org
Subject: Re: Commit and Exception Block
In-reply-to: <a7dacaf0474d48deaf82fe9ad6289ed9@kpn.com>
References: <05e4b1ba5e4741e08f63c113b5dd5ef7@kpn.com>
 <a7dacaf0474d48deaf82fe9ad6289ed9@kpn.com>
Comments: In-reply-to <soumik.bhattacharjee@kpn.com>
	message dated "Fri, 08 Oct 2021 08:00:34 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <231421.1633705396.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 08 Oct 2021 11:03:16 -0400
Message-ID: <231422.1633705396@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/231422.1633705396%40sss.pgh.pa.us>
Precedence: bulk

<soumik.bhattacharjee@kpn.com> writes:
> I have a procedure that may encounter an exception. I want to have an ex=
ception handling block where exception is to catch is any FK violations.
> Could you please suggest where it's getting missed as part of a transact=
ion.

I think you're confused about the scope of the exception block.
The syntax is

	BEGIN
	  some code here that might throw an exception
	EXCEPTION
	  some WHEN clauses here to catch exceptions from the covered code
	END

You wrote:

>    begin
>     RAISE SQLSTATE 'MYERR';
>       EXCEPTION
>       WHEN ...

So this exception block can *only* trap errors arising from that one
RAISE command, not anything earlier in the procedure.  Seems unlikely
that's what you wanted.

			regards, tom lane