Reference¶
This section provides lookup-oriented reference material for RockLake. Unlike the conceptual documentation (which explains WHY things work the way they do) or the architecture documentation (which explains HOW components fit together), reference pages are designed for quick answers to specific questions. You come here when you need to know what error code 42P01 means, what environment variable controls the cache size, what fields a table row contains, or what SQL patterns DuckDB sends.
The reference section is exhaustive rather than instructive. Every supported SQL statement is listed. Every error code is documented. Every environment variable is described. Every metric is named and explained. This is the section you bookmark and return to repeatedly during development, debugging, and operations.
How to Use This Section¶
Each page covers a single reference domain:
-
Complete list of all 28 catalog table types stored in the RockLake catalog. For each table: the tag byte, protobuf message fields, key encoding format, sort behavior, and relationship to other tables. This is the authoritative specification of the catalog schema.
-
Exhaustive list of every SQL statement pattern that RockLake's bounded classifier recognizes. Organized by category (schema operations, table operations, column operations, data file operations, transaction management). Includes the exact SQL format DuckDB sends and what catalog operation it maps to.
-
All SQLSTATE error codes returned by RockLake, organized by error class. For each code: name, description, common causes, and recommended handling. Stable across versions — safe for programmatic error handling.
-
Complete configuration reference. Every environment variable recognized by RockLake: purpose, type, default value, and examples. Includes storage credentials, server settings, TLS, logging, and performance tuning.
-
All Prometheus metrics exposed by RockLake's
/metricsendpoint. For each metric: type (counter, gauge, histogram), labels, description, and what it tells you about system health and performance. -
Definitions of all terms used throughout the documentation. If you encounter an unfamiliar word in any RockLake page, look it up here. Alphabetically organized for quick lookup.
Quick Links¶
| I need to know... | Go to... |
|---|---|
| What fields does a table row have? | Catalog Tables |
| What SQL creates a schema? | Supported SQL |
| What does error 57P04 mean? | Error Codes |
| How do I set the cache size? | Environment Variables |
| What metrics show read latency? | Metrics |
| What is "excision"? | Glossary |
Conventions¶
Throughout this section:
- Required means the system will not start without this value
- Default is the value used when nothing is explicitly configured
- Stable means the value/behavior will not change without a major version bump
- Types use Rust notation:
u64(unsigned 64-bit integer),string(UTF-8),bool(true/false),Option<T>(may be absent)