Re: WHEN SQLSTATE '00000' THEN equals to WHEN OTHERS THEN

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: David Fiedler <david.fido.fiedler@gmail.com>
Cc: pgsql-docs@lists.postgresql.org
Date: 2025-03-19T15:29:50Z
Lists: pgsql-hackers, pgsql-docs
David Fiedler <david.fido.fiedler@gmail.com> writes:
> I've stumbled across a code that used this condition, resulting in
> unexpected behavior. I think it worths a note that catching 00000 is not
> possible and that it results in a catch all handler.

Hmph.  The code thinks

	 * OTHERS is represented as code 0 (which would map to '00000', but we
	 * have no need to represent that as an exception condition).

but it evidently didn't consider the possibility of a user writing
'00000'.  I'm more inclined to consider this a bug and change plpgsql
to use something else internally to represent OTHERS.  We could use
-1, which AFAICS cannot be generated by MAKE_SQLSTATE.

			regards, tom lane



Commits

  1. plpgsql: make WHEN OTHERS distinct from WHEN SQLSTATE '00000'.