RE: Hardwired MAXBACKENDS limit could be history

Поиск
Список
Период
Сортировка
От Mikheev, Vadim
Тема RE: Hardwired MAXBACKENDS limit could be history
Дата
Msg-id 8F4C99C66D04D4118F580090272A7A234D32C0@sectorbase1.sectorbase.com
обсуждение исходный текст
Ответ на Hardwired MAXBACKENDS limit could be history  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Hardwired MAXBACKENDS limit could be history  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
> I'm not thinking about getting this done in time for 7.1, but I think
> it'd be a nice cleanup for 7.2.
> 
> Bruce, a TODO item please:
>   * Remove compile-time upper limit on number of backends 
> (MAXBACKENDS)

Did you ever consider remove per-backend semaphores at all?
We use them to sleep waiting for lock (ie when someone awake
us by changing our semaphore) - why don't use sigpause and
some signal? Semaphores are good to sync access to *shared*
resources but it's not that case here.

Vadim


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Jan Wieck
Дата:
Сообщение: Re: Open 7.1 items
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Hardwired MAXBACKENDS limit could be history