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

20.1 known limitations #7118

Merged
merged 1 commit into from
Apr 18, 2020
Merged

20.1 known limitations #7118

merged 1 commit into from
Apr 18, 2020

Conversation

jseldess
Copy link
Contributor

Add new limitations and remove resolved limitations.

@cockroach-teamcity
Copy link
Member

This change is Reviewable

@jseldess jseldess force-pushed the 20.1-known-limitations branch from 0203482 to 127fa47 Compare April 13, 2020 13:36
@awoods187
Copy link
Contributor

@lucy-zhang @jordanlewis and @RaduBerinde are there any other known limitations that can be lifted for 20.1?

@jseldess jseldess force-pushed the 20.1-known-limitations branch from 394a624 to ce25c3f Compare April 16, 2020 17:44
@jseldess jseldess changed the title [WIP] 20.1 known limitations 20.1 known limitations Apr 16, 2020
@jseldess
Copy link
Contributor Author


v20.1/known-limitations.md, line 60 at r1 (raw file):

[Tracking Github Issue](https://github.com/cockroachdb/cockroach/issues/43177)

### Concurrent SQL shells overwrite each other's history

@knz, PTAL.

@jseldess
Copy link
Contributor Author


v20.1/known-limitations.md, line 78 at r1 (raw file):

## Unresolved limitations

### Enterprise `BACKUP` does not capture database/table/column comments

@knz, PTAL.

@jseldess
Copy link
Contributor Author


v20.1/known-limitations.md, line 11 at r1 (raw file):

## New limitations

### `ROLLBACK TO SAVEPOINT` in high-priority transactions containing DDL

@knz, PTAL.

@jseldess
Copy link
Contributor Author


v20.1/known-limitations.md, line 28 at r1 (raw file):

[Tracking Github Issue](https://github.com/cockroachdb/cockroach/issues/46414)

### Column name from an outer column inside a subquery differs from PostgreSQL

@RaduBerinde, PTAL.

@jseldess
Copy link
Contributor Author


v20.1/known-limitations.md, line 54 at r1 (raw file):

[Tracking Github Issue](https://github.com/cockroachdb/cockroach/issues/46563)

### Privileges required to access to certain virtual tables differs from PostgreSQL

@knz, PTAL.

@jseldess jseldess force-pushed the 20.1-known-limitations branch from ce25c3f to 3d68a98 Compare April 16, 2020 21:12
@RaduBerinde
Copy link
Member


v20.1/known-limitations.md, line 28 at r1 (raw file):

Previously, jseldess (Jesse Seldess) wrote…

@RaduBerinde, PTAL.

Looks great, thanks!

@jseldess jseldess force-pushed the 20.1-known-limitations branch from 3d68a98 to 61e089a Compare April 17, 2020 19:11
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 7 of 7 files at r2.
Reviewable status: :shipit: complete! 0 of 0 LGTMs obtained (waiting on @jseldess)


v19.1/known-limitations.md, line 15 at r2 (raw file):

The [`COMMENT ON`](comment-on.html) statement associates comments to databases, tables, or columns. However, the internal table (`system.comments`) in which these comments are stored is not captured by enterprise [`BACKUP`](backup.html).

As a workaround, use the [`cockroach dump`](sql-dump.html) command, which emits `COMMENT ON` statements alongside `CREATE` statements.

I would recommend using the "schema only" for dump alongside BACKUP


v20.1/known-limitations.md, line 11 at r1 (raw file):

Previously, jseldess (Jesse Seldess) wrote…

@knz, PTAL.

that's good thanks


v20.1/known-limitations.md, line 54 at r1 (raw file):

Previously, jseldess (Jesse Seldess) wrote…

@knz, PTAL.

lgtm


v20.1/known-limitations.md, line 60 at r1 (raw file):

Previously, jseldess (Jesse Seldess) wrote…

@knz, PTAL.

lgtm


v20.1/known-limitations.md, line 78 at r1 (raw file):

Previously, jseldess (Jesse Seldess) wrote…

@knz, PTAL.

see my comment above

@jseldess jseldess force-pushed the 20.1-known-limitations branch from 61e089a to 4d65418 Compare April 18, 2020 19:40
Copy link
Contributor Author

@jseldess jseldess 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 (waiting on @jseldess, @knz, and @RaduBerinde)


v19.1/known-limitations.md, line 15 at r2 (raw file):

Previously, knz (kena) wrote…

I would recommend using the "schema only" for dump alongside BACKUP

Done.


v20.1/known-limitations.md, line 11 at r1 (raw file):

Previously, knz (kena) wrote…

that's good thanks

Thanks!


v20.1/known-limitations.md, line 28 at r1 (raw file):

Previously, RaduBerinde wrote…

Looks great, thanks!

Thanks!


v20.1/known-limitations.md, line 54 at r1 (raw file):

Previously, knz (kena) wrote…

lgtm

Thanks!


v20.1/known-limitations.md, line 60 at r1 (raw file):

Previously, knz (kena) wrote…

lgtm

Thanks!


v20.1/known-limitations.md, line 78 at r1 (raw file):

Previously, knz (kena) wrote…

see my comment above

Done.

@jseldess jseldess force-pushed the 20.1-known-limitations branch from 4d65418 to 3053645 Compare April 18, 2020 20:47
@jseldess jseldess merged commit 8402a51 into master Apr 18, 2020
@jseldess jseldess deleted the 20.1-known-limitations branch April 18, 2020 20:55
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.

5 participants