On Tue, Apr 21, 2015 at 8:08 AM, Andres Freund <and...@anarazel.de> wrote: > I've now named the functions: > > * pg_replication_origin_create > * pg_replication_origin_drop > * pg_replication_origin_get (map from name to id) > * pg_replication_progress_setup_origin : configure session to replicate > from a specific origin > * pg_replication_progress_reset_origin > * pg_replication_progress_setup_tx_details : configure per transaction > details (LSN and timestamp currently) > * pg_replication_progress_is_replaying : Is a origin configured for the > session > * pg_replication_progress_advance : "manually" set the replication > progress to a value. Primarily useful for copying values from other > systems and such. > * pg_replication_progress_get : How far did replay progress for a > certain origin > * pg_get_replication_progress : SRF returning the replay progress for > all origin. > > Any comments?
Why are we using functions for this rather than DDL? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers