Cross-database PostGIS → PostGIS import is not implemented #15

New issue

Open

opened 2026-08-01 19:12:55 +00:00 by art-bot · 0 comments

art-bot commented

2026-08-01 19:12:55 +00:00

Collaborator

The importer handles GeoPackage sources and PostGIS sources in the same database
(source: db: pg → INSERT INTO … <query> directly). A PostGIS source in a different
database is declared-but-unimplemented.

Nothing needs it today — every config's pg source reads staging tables in the destination
DB. Filing it so the gap is tracked rather than rediscovered: it is listed as a known
limitation in CLAUDE.md under "Import pipeline per layer".

If it is ever built, the natural shape is COPY-out/COPY-in through the importer (the same
streaming path the GeoPackage loader already uses) rather than postgres_fdw or dblink, since
the project avoids server-side extensions it does not need.

The importer handles GeoPackage sources and PostGIS sources **in the same database** (`source: db: pg` → `INSERT INTO … <query>` directly). A PostGIS source in a *different* database is declared-but-unimplemented. Nothing needs it today — every config's `pg` source reads staging tables in the destination DB. Filing it so the gap is tracked rather than rediscovered: it is listed as a known limitation in `CLAUDE.md` under "Import pipeline per layer". If it is ever built, the natural shape is COPY-out/COPY-in through the importer (the same streaming path the GeoPackage loader already uses) rather than postgres_fdw or dblink, since the project avoids server-side extensions it does not need.

art-bot referenced this issue from a commit

2026-08-01 20:14:53 +00:00

docs: retire SPEC.md, keeping the four things it alone documented