diff options
author | Fujii Masao <fujii@postgresql.org> | 2019-05-21 00:22:06 +0900 |
---|---|---|
committer | Fujii Masao <fujii@postgresql.org> | 2019-05-21 00:23:16 +0900 |
commit | fc7c281f87467c1ff24fd72e0cc313dd6a71873f (patch) | |
tree | 653d97cab2bad96d81bea6bff056f72bee19ae53 /src/backend/access/transam/xlog.c | |
parent | 3c439a58df83ae51f650cfae9878df1f9b70c4b8 (diff) | |
download | postgresql-fc7c281f87467c1ff24fd72e0cc313dd6a71873f.tar.gz postgresql-fc7c281f87467c1ff24fd72e0cc313dd6a71873f.zip |
Make VACUUM accept 1 and 0 as a boolean value.
Commit 41b54ba78e allowed existing VACUUM options to take a boolean
argument. It's documented that valid boolean values that VACUUM can
accept are true, false, on, off, 1, and 0. But previously the parser
failed to accept 1 and 0 as a boolean value in VACUUM syntax because
of a lack of NumericOnly clause for vac_analyze_option_arg in gram.y.
This commit adds such NumericOnly clause so that VACUUM options
can take also 1 and 0 as a boolean value.
Discussion: https://postgr.es/m/CAHGQGwGYg82A8UCQxZe7Zn9MnyUBGdyB=1CNpKF3jBny+RbyfA@mail.gmail.com
Diffstat (limited to 'src/backend/access/transam/xlog.c')
0 files changed, 0 insertions, 0 deletions