| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
| Subject: | Re: Time based lag tracking for logical replication |
| Date: | 2017-05-11 07:32:03 |
| Message-ID: | 20170511073203.GA828137@rfd.leadboat.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Apr 23, 2017 at 01:10:32AM +0200, Petr Jelinek wrote:
> The time based lag tracking commit [1] added interface for logging
> progress of replication so that we can report lag as time interval
> instead of just bytes. But the patch didn't contain patch for the
> builtin logical replication.
>
> So I wrote something that implements this.
This is listed as a PostgreSQL 10 open item, but the above makes it sound like
a feature to consider for v11, not a defect in v10. Why is this an open item?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2017-05-11 07:38:59 | Re: transition table behavior with inheritance appears broken (was: Declarative partitioning - another take) |
| Previous Message | Noah Misch | 2017-05-11 07:27:01 | Re: Re: logical replication syntax (was DROP SUBSCRIPTION, query cancellations and slot handling) |