Re: max_connections and standby server
| От | Tom Lane |
|---|---|
| Тема | Re: max_connections and standby server |
| Дата | |
| Msg-id | 28622.1439273213@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: max_connections and standby server (Michael Paquier <michael.paquier@gmail.com>) |
| Ответы |
Re: max_connections and standby server
|
| Список | pgsql-hackers |
Michael Paquier <michael.paquier@gmail.com> writes:
> On Tue, Aug 11, 2015 at 2:42 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Somebody refresh my memory as to why we have this restriction (that is,
>> slave's max_connections >= master's max_connections) in the first place?
>> Seems like it should not be a necessary requirement, and working towards
>> getting rid of it would be far better than any other answer.
> If I recall correctly, that's because KnownAssignedXIDs and the lock
> table need to be large enough on the standby for the largest snapshot
> possible (procarray.c).
Hm. Surely KnownAssignedXIDs could be resized at need. As for the shared
lock table on the standby, that could be completely occupied by locks
taken by hot-standby backend processes, so I don't see why we're insisting
on anything particular as to its size.
regards, tom lane
В списке pgsql-hackers по дате отправления: