-
Notifications
You must be signed in to change notification settings - Fork 451
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Session vars updates #3799
Session vars updates #3799
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewable status:
complete! 0 of 0 LGTMs obtained
v2.1/set-vars.md, line 58 at r2 (raw file):
`client_min_messages` | Ignored; recognized for compatibility with PostgreSQL clients. Only possible value is `notice`. | N/A | Yes `standard_conforming_strings` | Ignored; recognized for compatibility with PostgreSQL clients. | N/A | Yes `integer_datetimes` | Ignored; recognized for compatibility with PostgreSQL clients. Only possible value is `on`. | N/A | Yes
Should standard_conforming_strings
and integer_datetimes
have the "New in v2.1" tag? I was thinking no, since they are only there for Postgres compatibility, but would like opinions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed 2 of 2 files at r2.
Reviewable status:complete! 0 of 0 LGTMs obtained
v2.1/set-vars.md, line 58 at r2 (raw file):
Previously, lhirata wrote…
Should
standard_conforming_strings
andinteger_datetimes
have the "New in v2.1" tag? I was thinking no, since they are only there for Postgres compatibility, but would like opinions.
I agree you do not need to mark them as new.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Closes #3614.
Closes #3615.
Closes #3618.