summaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistxlog.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2017-03-07 10:42:11 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2017-03-07 10:42:18 -0500
commit11324e408f0e3a25621c611467927c644894b30d (patch)
treeddfa645887b4a99e67c11a12fa3b721884ef4300 /src/backend/access/gist/gistxlog.c
parenta71f10189dc10a2fe422158a2c9409e0f77c6b9e (diff)
downloadpostgresql-11324e408f0e3a25621c611467927c644894b30d.tar.gz
Remove vestigial grammar support for CHARACTER ... CHARACTER SET option.
The SQL standard says that you should be able to write "CHARACTER SET foo" as part of the declaration of a char-type column. We don't implement that, but a rough form of support has existed in gram.y since commit f10b63923. That's now sat there for nigh 20 years without anyone fleshing it out --- and even if someone did, the contemplated approach of having separate data type name(s) for every character set certainly isn't what we'd do today. Let's just remove the grammar production; if anyone is ever motivated to work on this, reinventing the grammar support is a trivial fraction of what they'd have to do. And we've never documented anything about supporting such a clause. Per gripe from Neha Khatri. Discussion: https://postgr.es/m/CAFO0U+-iOS5oYN5v3SBuZvfhPUTRrkDFEx8w7H17B07Rwg3YUA@mail.gmail.com
Diffstat (limited to 'src/backend/access/gist/gistxlog.c')
0 files changed, 0 insertions, 0 deletions