| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_basebackups and slots |
| Date: | 2016-12-19 21:35:13 |
| Message-ID: | 342369ae-0bd1-e8e1-bdd3-698413bdd1cc@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 12/17/16 9:55 AM, Magnus Hagander wrote:
> That makes a lot of sense now that we have temporary replication slots,
> I agree. And then max_replication_slots could be something like
> persistent_replication_slots?
I was thinking was more like that each walsender gets one fixed slot,
which can be temporary or persistent.
Or maybe default max_replication_slots to something like -1, which means
equal to max_wal_senders.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2016-12-19 21:37:33 | Re: Proposal: add error message in backend/catalog/index.c |
| Previous Message | Peter Eisentraut | 2016-12-19 21:29:51 | Re: Proposal for changes to recovery.conf API |