aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/jsonfuncs.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2022-12-11 12:56:54 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2022-12-11 12:56:54 -0500
commitb8c0ffbd2c8038fbebe76b48616860a7efec66ae (patch)
tree35bf850a377d63902da6a95747374e5b46e36419 /src/backend/utils/adt/jsonfuncs.c
parentc60c9badba9b4db3155eef081ae0b923f983168c (diff)
downloadpostgresql-b8c0ffbd2c8038fbebe76b48616860a7efec66ae.tar.gz
postgresql-b8c0ffbd2c8038fbebe76b48616860a7efec66ae.zip
Convert domain_in to report errors softly.
This is straightforward as far as it goes. However, it does not attempt to trap errors occurring during the execution of domain CHECK constraints. Since those are general user-defined expressions, the only way to do that would involve starting up a subtransaction for each check. Of course the entire point of the soft-errors feature is to not need subtransactions, so that would be self-defeating. For now, we'll rely on the assumption that domain checks are written to avoid throwing errors. Discussion: https://postgr.es/m/1181028.1670635727@sss.pgh.pa.us
Diffstat (limited to 'src/backend/utils/adt/jsonfuncs.c')
0 files changed, 0 insertions, 0 deletions