aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/jsonfuncs.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2020-01-23 16:15:32 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2020-01-23 16:15:32 -0500
commit9a3a75cb81d3b060b8e76001d04c78ab4ce0dcef (patch)
treee266ac0f2d9d517bf2bec5228b387cda17474245 /src/backend/utils/adt/jsonfuncs.c
parent4c70098ffa8cf19e79e7b124ccac05dd338c937b (diff)
downloadpostgresql-9a3a75cb81d3b060b8e76001d04c78ab4ce0dcef.tar.gz
postgresql-9a3a75cb81d3b060b8e76001d04c78ab4ce0dcef.zip
Fix an oversight in commit 4c70098ff.
I had supposed that the from_char_seq_search() call sites were all passing the constant arrays you'd expect them to pass ... but on looking closer, the one for DY format was passing the days[] array not days_short[]. This accidentally worked because the day abbreviations in English are all the same as the first three letters of the full day names. However, once we took out the "maximum comparison length" logic, it stopped working. As penance for that oversight, add regression test cases covering this, as well as every other switch case in DCH_from_char() that was not reached according to the code coverage report. Also, fold the DCH_RM and DCH_rm cases into one --- now that seq_search is case independent, there's no need to pass different comparison arrays for those cases. Back-patch, as the previous commit was.
Diffstat (limited to 'src/backend/utils/adt/jsonfuncs.c')
0 files changed, 0 insertions, 0 deletions