| From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | fabiogibon(at)gmail(dot)com |
| Subject: | BUG #16048: SQLSTATE 22P05 is not captured in exception clause |
| Date: | 2019-10-11 14:03:35 |
| Message-ID: | 16048-ff86833b63f1a0a2@postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 16048
Logged by: Fabio Henrique Gibon
Email address: fabiogibon(at)gmail(dot)com
PostgreSQL version: 12.0
Operating system: Windows
Description:
Hi,
I have a database using LATIN1 (and I can't change it), so, when the
user informar a invalid character it is not captured in exception clause.
See a short sample:
DO $$
DECLARE
v varchar;
BEGIN
v := 'ABCŸ';
EXCEPTION
WHEN others THEN
RAISE INFO 'Error State: %', SQLSTATE;
END$$;
I tried in old versions (9.0, 9.6,...) and the result is the same. The error
is propagated, disregarding the exception treatement.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2019-10-11 14:12:49 | BUG #16049: log_line_prefix=%a and log_connections - application_name missing |
| Previous Message | Michael Paquier | 2019-10-11 00:28:14 | Re: BUG #16039: PANIC when activating replication slots in Postgres 12.0 64bit under Windows |