| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Petr Jelinek <petr(at)2ndquadrant(dot)com>, Steve Singer <steve(at)ssinger(dot)info>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Replication identifiers, take 4 |
| Date: | 2015-04-21 20:26:08 |
| Message-ID: | CA+TgmoY7cqW6-7798w5qcvZVw91mvVc=xdaGW6Fo2ms4Q4=F9w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Apr 21, 2015 at 8:08 AM, Andres Freund <andres(at)anarazel(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2015-04-21 20:27:58 | Re: Freeze avoidance of very large table. |
| Previous Message | Andres Freund | 2015-04-21 20:25:02 | Re: Reducing spinlock acquisition within clock sweep loop |