Skip to content
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

Merged
merged 2 commits into from
Oct 2, 2018
Merged

Session vars updates #3799

merged 2 commits into from
Oct 2, 2018

Conversation

lnhsingh
Copy link
Contributor

@lnhsingh lnhsingh commented Oct 1, 2018

Closes #3614.
Closes #3615.
Closes #3618.

Closes #3614. Closes #3615. Closes #3618.
@cockroach-teamcity
Copy link
Member

This change is Reviewable

Copy link
Contributor Author

@lnhsingh lnhsingh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewable status: :shipit: 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.

Copy link
Contributor

@knz knz left a 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: :shipit: complete! 0 of 0 LGTMs obtained


v2.1/set-vars.md, line 58 at r2 (raw file):

Previously, lhirata wrote…

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.

I agree you do not need to mark them as new.

Copy link
Contributor

@rmloveland rmloveland left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@lnhsingh lnhsingh merged commit d39929d into master Oct 2, 2018
@lnhsingh lnhsingh deleted the session-vars branch October 2, 2018 16:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants