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

Capture required catalogs information #27

Closed
4 tasks
rjuju opened this issue Dec 29, 2019 · 1 comment
Closed
4 tasks

Capture required catalogs information #27

rjuju opened this issue Dec 29, 2019 · 1 comment
Assignees

Comments

@rjuju
Copy link
Member

rjuju commented Dec 29, 2019

Naive initial list:

  • pg_class(oid, relname, relnamespace, relkind)
  • pg_attribute(oid, attname, attrelid, atttypid)
  • pg_namespace(oid, nspname)
  • pg_type(oid, typname)

This obviously shouldn't been for all databases and all snapshots, so some heuristics will have to be added to know when to perform that. Some ideas for that:

  • Cache the current ShmemVariableCache->nextOid for each server and the highest recorded oid found in each database
  • let user ask for refreshing that data from the UI, propagated to the collector
  • use ProcessUtility_hook to detect when handled objects have been created or dropped
@rjuju rjuju added this to the v4.1 milestone Dec 29, 2019
@rjuju rjuju self-assigned this Dec 10, 2023
@rjuju rjuju removed this from the v4.1 milestone Dec 10, 2023
@rjuju
Copy link
Member Author

rjuju commented Dec 10, 2023

Per-database catalog snapshot and a button to force a refresh from the UI have been added in the v5 version, so closing this issue.

@rjuju rjuju closed this as completed Dec 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant