Re: Replication identifiers, take 4 - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Replication identifiers, take 4
Date
Msg-id CA+TgmoY7cqW6-7798w5qcvZVw91mvVc=xdaGW6Fo2ms4Q4=F9w@mail.gmail.com
Whole thread Raw
In response to Re: Replication identifiers, take 4  (Andres Freund <andres@anarazel.de>)
Responses Re: Replication identifiers, take 4
List pgsql-hackers
On Tue, Apr 21, 2015 at 8:08 AM, Andres Freund <andres@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



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Reducing spinlock acquisition within clock sweep loop
Next
From: Andres Freund
Date:
Subject: Re: Freeze avoidance of very large table.