Re: [HACKERS] pg_basebackups and slots - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [HACKERS] pg_basebackups and slots
Date
Msg-id 342369ae-0bd1-e8e1-bdd3-698413bdd1cc@2ndquadrant.com
Whole thread Raw
In response to Re: [HACKERS] pg_basebackups and slots  (Magnus Hagander <magnus@hagander.net>)
List 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



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] Proposal for changes to recovery.conf API
Next
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] Proposal: add error message in backend/catalog/index.c