Retail DDL
summary
Retail DDL is an extension of about thirty server-side functions that generate CREATE/ALTER SQL for individual objects so you avoid pg_dump’s overhead and locks; it runs in plpgsql, returns canonical output (schema, WITH OIDS, ACLs optional), covers tables, views, indexes, triggers and more, already produces useful DDL quickly and reliably, and is designed as a building block for schema-integrity checks with planned additions for serial handling and comments. server-side functions no locks canonical output plpgsql extension
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:40The problem
- 4:03PGdump
- 10:12Schema name
- 13:54Serial
- 15:27Check constraint
- 18:30NonConstraint Index DDL
- 21:43Implementation
- 23:29Compatibility
- 25:48pgadmin
- 28:00psql commands
- 29:02psql generate
- 30:39rigproc
- 32:13Kitchen Sink
- 34:51Tabs
- 35:33Core vs SQL
- 37:23ACL Display
- 39:01Wrapup
related talks
56mLogical Replication of DDLs
33mTips and tricks for the Oracle Database developer
29mDuckPL: A procedural language in DuckDB
32mAnonymizing Data in Postgres Without Losing Your Mind (or Your
21mDeep dive: Data loading
51mWhen Postgres Can't, You Can!
15mDDLumos: Understanding and Detecting Atomic DDL Bugs in DBMSs
36mNORM: No ORM Framework