max_prepared_transactions default ... why 5?

Поиск
Список
Период
Сортировка
От Josh Berkus
Тема max_prepared_transactions default ... why 5?
Дата
Msg-id 200710172124.42386.josh@agliodbs.com
обсуждение исходный текст
Ответы Re: max_prepared_transactions default ... why 5?  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Folks,

I'm writing up the new GUCs, and noticed that max_prepared_transactions 
defaults to 5.  This is too many for most applications (which don't use them 
at all) and far too few for applications which use them regularly.  

It seems like we should either set the value to 0, or to something higher, 
like 50.

It would also be nice to be able to just set the value to be equal to 
max_connections automatically, but I'm sure I brought that point up too late. 

-- 
Josh Berkus
PostgreSQL @ Sun
San Francisco


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

Предыдущее
От: Tom Lane
Дата:
Сообщение: ts_rewrite bug?
Следующее
От: Tom Lane
Дата:
Сообщение: Re: max_prepared_transactions default ... why 5?