Ryan Malloy
3915d1784f
An existing product called PG Orbit (a mobile PostgreSQL client) creates a naming conflict. pg_orrery — a database orrery built from Keplerian parameters and SQL instead of brass gears. Build system: control file, Makefile, Dockerfile, docker init script. C source: GUC prefix, PG_FUNCTION_INFO_V1 symbol, header guards, ereport prefixes, comments across ~30 files including vendored SGP4. SQL: all 5 install/migration scripts, function name pg_orrery_ephemeris_info. Tests: 9 SQL suites, 8 expected outputs, standalone DE reader test. Documentation: CLAUDE.md, README.md, DESIGN.md, Starlight site infra, 36 MDX pages, OG renderer, logo SVG, docker-compose, agent threads. All 13 regression suites pass. Docs site builds (37 pages).
11 lines
357 B
Bash
Executable File
11 lines
357 B
Bash
Executable File
#!/bin/bash
|
|
set -e
|
|
|
|
# Create the pg_orrery extension on first container startup.
|
|
# The 020_ prefix orders this after TimescaleDB's own init scripts
|
|
# (000_, 001_, 010_) when used in timescaledb-ha images.
|
|
|
|
psql -v ON_ERROR_STOP=1 --username "$POSTGRES_USER" --dbname "${POSTGRES_DB:-postgres}" <<-'EOSQL'
|
|
CREATE EXTENSION IF NOT EXISTS pg_orrery;
|
|
EOSQL
|