-
Notifications
You must be signed in to change notification settings - Fork 596
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
feat: support pg_stat_user_tables and key_column_usage #19739
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.
LGTM, can we add some reliable e2e for them like https://github.com/risingwavelabs/risingwave/blob/main/e2e_test/batch/catalog/issue_8791.slt.part, for example:
select * from information_schema.key_column_usage where 1 != 1;
Sure. Will do |
e330eb2
to
452d006
Compare
/// The view `key_column_usage` contains all constraints belonging to tables that the current user owns or has some privilege other than SELECT on. | ||
/// Ref: [`https://www.postgresql.org/docs/current/infoschema-key-column-usage.html`] | ||
/// Limitation: | ||
/// This view assume the constraint schema is the same as the table schema, since `pg_clatalog`.`pg_constraint` only support primrary key. |
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.
There's a typo in the comment: primrary
should be primary
in the limitation note. Also, there's a typo in pg_clatalog
which should be pg_catalog
.
The corrected comment should read: "...since pg_catalog.pg_constraint
only supports primary key."
Spotted by Graphite Reviewer
Is this helpful? React 👍 or 👎 to let us know.
I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Resolves #17753
Checklist
./risedev check
(or alias,./risedev c
)Documentation
Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.