Re: BUG #3801: max_fsm_pages postgresql.conf default != guc.c default
| От | Kris Jurka |
|---|---|
| Тема | Re: BUG #3801: max_fsm_pages postgresql.conf default != guc.c default |
| Дата | |
| Msg-id | Pine.BSO.4.64.0712062135120.2548@leary.csoft.net обсуждение исходный текст |
| Ответ на | Re: BUG #3801: max_fsm_pages postgresql.conf default != guc.c default (Reece Hart <reece@harts.net>) |
| Ответы |
Re: BUG #3801: max_fsm_pages postgresql.conf default !=
guc.c default
|
| Список | pgsql-bugs |
On Thu, 6 Dec 2007, Reece Hart wrote: > This seems to directly say that the commented out settings are the > default values, and furthermore that one must restart to get the > indicated default back. Based on your evidence, it seems that the > postgresql.conf comment for max_fsm_pages needs revising to indicate > that the m_f_p default is determined at initdb-time. Yes, the commented out values are the defaults, but after initdb max_fsm_pages is not commented out, which is why I'm suggesting you or some other admin modified your file. Try this test: $ ./tmp/82/bin/initdb -D fsmtest > fsmlog 2>&1 $ grep max_fsm fsmlog selecting default shared_buffers/max_fsm_pages ... 24MB/153600 $ grep max_fsm_pages fsmtest/postgresql.conf max_fsm_pages = 153600 # min max_fsm_relations*16, 6 bytes each So you can see max_fsm_pages is not commented out, so it is not the true default (20000). Kris Jurka
В списке pgsql-bugs по дате отправления: