diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2014-12-02 18:23:16 -0500 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2014-12-02 18:23:27 -0500 |
commit | 475aedd1ef0c0f9fc9d675dd2286380d14804975 (patch) | |
tree | b237c4f2504714f8dc8ee3fca32754ef0a106abc /src/backend/access/transam/commit_ts.c | |
parent | 0fd38e13706e6bd4b2a4ce4e0570d0aa4ad65345 (diff) | |
download | postgresql-475aedd1ef0c0f9fc9d675dd2286380d14804975.tar.gz postgresql-475aedd1ef0c0f9fc9d675dd2286380d14804975.zip |
Improve error messages for malformed array input strings.
Make the error messages issued by array_in() uniformly follow the style
ERROR: malformed array literal: "actual input string"
DETAIL: specific complaint here
and rewrite many of the specific complaints to be clearer.
The immediate motivation for doing this is a complaint from Josh Berkus
that json_to_record() produced an unintelligible error message when
dealing with an array item, because it tries to feed the JSON-format
array value to array_in(). Really it ought to be smart enough to
perform JSON-to-Postgres array conversion, but that's a future feature
not a bug fix. In the meantime, this change is something we agreed
we could back-patch into 9.4, and it should help de-confuse things a bit.
Diffstat (limited to 'src/backend/access/transam/commit_ts.c')
0 files changed, 0 insertions, 0 deletions