aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/jsonfuncs.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2018-04-23 15:29:11 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2018-04-23 15:29:11 -0400
commit4df58f7ed7f9ddc5a3196fcbad35690d1b3218de (patch)
treeb29e08a24c1bb4066cb4e509b076103cf0206fb7 /src/backend/utils/adt/jsonfuncs.c
parentdf044026fcaf60b22291c31f4290a3b09ecf5833 (diff)
downloadpostgresql-4df58f7ed7f9ddc5a3196fcbad35690d1b3218de.tar.gz
postgresql-4df58f7ed7f9ddc5a3196fcbad35690d1b3218de.zip
Fix handling of partition bounds for boolean partitioning columns.
Previously, you could partition by a boolean column as long as you spelled the bound values as string literals, for instance FOR VALUES IN ('t'). The trouble with this is that ruleutils.c printed that as FOR VALUES IN (TRUE), which is reasonable syntax but wasn't accepted by the grammar. That results in dump-and-reload failures for such cases. Apply a minimal fix that just causes TRUE and FALSE to be converted to strings 'true' and 'false'. This is pretty grotty, but it's too late for a more principled fix in v11 (to say nothing of v10). We should revisit the whole issue of how partition bound values are parsed for v12. Amit Langote Discussion: https://postgr.es/m/e05c5162-1103-7e37-d1ab-6de3e0afaf70@lab.ntt.co.jp
Diffstat (limited to 'src/backend/utils/adt/jsonfuncs.c')
0 files changed, 0 insertions, 0 deletions