DDL replication#
DDL stands for data definition language, the subset of the SQL language that creates, alters, and drops database objects.
PGD provides automatic DDL replication, which makes certain DDL changes easier. With automatic replication, you don’t have to manually distribute the DDL change to all nodes and ensure that they’re consistent.
This section looks at how DDL replication is handled in PGD.
DDL overview provides a general outline of what PGD’s DDL replication is capable of.
DDL locking details examines how DDL replication uses locks to safely replicate DDL.
Managing DDL with PGD replication gives best practice advice on why and how to limit the impact of DDL changes so they don’t overly affect the smooth running of the cluster.
DDL and role manipulation statements notes issues around manipulating roles over multiple databases in a cluster.
Workarounds for DDL restrictions gives a range of options for handling situations where DDL replication may present restrictions, such as altering columns, constraints, and types.
PGD functions that behave like DDL details the PGD functions that behave like DDL and therefore behave in a similar way and are subject to similar restrictions.
- DDL overview
- DDL replication options
- DDL locking details
- Managing DDL with PGD replication
- DDL command handling matrix
- Command matrix
- Command notes
- ALTER SEQUENCE
- ALTER TABLE
- ALTER TABLE disallowed commands
- ALTER TABLE locking
- ALTER TABLE examples
- ALTER TYPE
- COMMENT ON
- CREATE PROFILE or ALTER PROFILE
- CREATE TABLE AS and SELECT INTO
- EXPLAIN
- EXPLAIN ANALYZE Replication
- EXPLAIN ANALYZE Locking
- GRANT and REVOKE
- LOCK TABLE
- MATERIALIZED VIEW
- SECURITY LABEL
- TRUNCATE Replication
- TRUNCATE Locking
- DDL and role manipulation statements
- Workarounds for DDL restrictions
- PGD functions that behave like DDL