aboutsummaryrefslogtreecommitdiff
path: root/src/backend/regex/regerror.c
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2002-08-06 05:24:04 +0000
committerBruce Momjian <bruce@momjian.us>2002-08-06 05:24:04 +0000
commita6c768199734b28e1d32f2088211a0d5350dd5e2 (patch)
tree4259d267cca6cbb7bd661eb3a74c04d350ac728c /src/backend/regex/regerror.c
parent5df307c7782518c4a3c19ffd05c7cb591b97e23c (diff)
downloadpostgresql-a6c768199734b28e1d32f2088211a0d5350dd5e2.tar.gz
postgresql-a6c768199734b28e1d32f2088211a0d5350dd5e2.zip
This patch changes the behavior of PostgreSQL so that if any queries are
executed in an implicitely aborted transaction (e.g. after an occur occurs), we return an error (and not just a warning). For example: nconway=# begin; BEGIN nconway=# insert; -- syntax error ERROR: parser: parse error at or near ";" nconway=# select * from a; ERROR: current transaction is aborted, queries ignored until end of transaction block The old behavior was: nconway=# begin; BEGIN nconway=# insert; ERROR: parser: parse error at or near ";" nconway=# select * from a; WARNING: current transaction is aborted, queries ignored until end of transaction block *ABORT STATE* Which can be confusing: if the client isn't paying careful attention, they will conclude that the query has executed (because no error is returned). Neil Conway
Diffstat (limited to 'src/backend/regex/regerror.c')
0 files changed, 0 insertions, 0 deletions