diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2017-05-26 12:51:05 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2017-05-26 12:51:05 -0400 |
| commit | a561254e4c620ca9d62044520bd05cfe687f786c (patch) | |
| tree | 6210153bccbaed1866fb70ac6ddc5db5b0612756 /contrib/postgres_fdw/postgres_fdw.c | |
| parent | 1218abc47e859c3f98030558e93942636e12af0d (diff) | |
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 'contrib/postgres_fdw/postgres_fdw.c')
0 files changed, 0 insertions, 0 deletions