Skip to content

Conversation

angles-n-daemons
Copy link
Contributor

As part of an effort to define a more stable sql interface for the introspection of cockroach specific internals, we'll port the zones table (and a number of other "production ready" crdb_internal tables) to the information_schema.

The system.eventlog table is unique, in that it is the only table we plan on porting to the information_schema which is not a virtual table, and therefore should require some extra steps.

Fixes: #149907
Epic: CRDB-24527

Release note (sql change): Adds a view to the system.eventlog in the information_schema.

As part of an effort to define a more stable sql interface for the
introspection of cockroach specific internals, we'll port the zones
table (and a number of other "production ready" crdb_internal tables) to
the information_schema.

The system.eventlog table is unique, in that it is the only table we
plan on porting to the information_schema which is not a virtual table,
and therefore should require some extra steps.

Fixes: cockroachdb#149907
Epic: CRDB-24527

Release note (sql change): Adds a view to the system.eventlog in the
information_schema.
@angles-n-daemons angles-n-daemons requested a review from a team as a code owner September 5, 2025 21:17
Copy link

blathers-crl bot commented Sep 5, 2025

It looks like your PR touches production code but doesn't add or edit any test code. Did you consider adding tests to your PR?

🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.

@cockroach-teamcity
Copy link
Member

This change is Reviewable

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.

sql: port eventlog to the information_schema
2 participants