aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistutil.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2017-05-26 12:51:05 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2017-05-26 12:51:05 -0400
commit5886c7d5893f88efe5de0bf78d9a1439d09c004a (patch)
tree3e45ef316f44a60cb69b71a8391c13f2db1dd217 /src/backend/access/gist/gistutil.c
parent50d9476920b5c0dac159247c4e640a1519396cee (diff)
downloadpostgresql-5886c7d5893f88efe5de0bf78d9a1439d09c004a.tar.gz
postgresql-5886c7d5893f88efe5de0bf78d9a1439d09c004a.zip
Fix pg_dump to not emit invalid SQL for an empty operator class.
If an operator class has no operators or functions, and doesn't need a STORAGE clause, we emitted "CREATE OPERATOR CLASS ... AS ;" which is syntactically invalid. Fix by forcing a STORAGE clause to be emitted anyway in this case. (At some point we might consider changing the grammar to allow CREATE OPERATOR CLASS without an opclass_item_list. But probably we'd want to omit the AS in that case, so that wouldn't fix this pg_dump issue anyway.) It's been like this all along, so back-patch to all supported branches. Daniel Gustafsson, tweaked by me to avoid a dangling-pointer bug Discussion: https://postgr.es/m/D9E5FC64-7A37-4F3D-B946-7E4FB468F88A@yesql.se
Diffstat (limited to 'src/backend/access/gist/gistutil.c')
0 files changed, 0 insertions, 0 deletions