catalog

Schema reference for the catalog and catalog_latest SQL views — full catalog JSON snapshots produced by catalogers, with history over time.

catalog
catalog_latest

The catalog view provides a historical timeseries of catalog JSONs generated by running catalogers over time. Each row is a complete catalog snapshot at a point in time.

The catalog_latest view holds only the current catalog. It is guaranteed to return at most one row, and no rows until Lunar Hub has published a configuration manifest.

Schema

Both views share the same columns.

Column	Type	Description
timestamp	TIMESTAMP	When the catalog last changed
captured_at	TIMESTAMP	When this version was recorded. NULL on the newest row when the current catalog has changed since the last recording. catalog only
catalog_json	JSONB	The complete catalog data in JSON format

Notes

• The catalog JSON contains the full inventory of components and their metadata. The format is defined on the Catalog JSON page
• catalog_latest returns the same document as lunar cataloger get-json, so a query and the CLI always agree
• timestamp is when the catalog last changed — it does not advance when a cataloger runs and produces the same result
• The history is sampled, not exhaustive. Versions are recorded periodically, so several changes landing close together may appear as one row. A catalog that changes and changes back between recordings leaves no trace
• History begins when your Lunar Hub was upgraded to record it. Catalogs from before that point are not available here — use lunar cataloger get-json --ts, which reconstructs any past catalog from the cataloger delta history
• Order the history by captured_at, not by timestamp. timestamp reflects when the catalog changed and can repeat across rows; captured_at always increases

Usage examples

Get the current catalog:

SELECT timestamp, catalog_json
FROM catalog_latest;

Track how the component count has changed over time:

SELECT captured_at,
       jsonb_array_length(jsonb_path_query_array(catalog_json, '$.components.*')) AS components
FROM catalog
ORDER BY captured_at NULLS LAST;

List every component in the catalog with its domain and owner:

SELECT component.key              AS component,
       component.value->>'domain' AS domain,
       component.value->>'owner'  AS owner
FROM catalog_latest,
     jsonb_each(catalog_json->'components') AS component
ORDER BY component;

Fetch the catalog only when it has changed since you last looked. The timestamp filter is evaluated before the document is assembled, so a poll that finds nothing new is cheap — prefer this to re-fetching the whole document on a schedule:

SELECT timestamp, catalog_json
FROM catalog_latest
WHERE timestamp > '2026-08-10 12:00:00';

For per-component queries, the components view is usually a better fit than unpacking this document — it is row-shaped and indexed.