From: | Kris Jurka <books(at)ejurka(dot)com> |
---|---|
To: | Reece Hart <reece(at)harts(dot)net> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #3801: max_fsm_pages postgresql.conf default != guc.c default |
Date: | 2007-12-07 02:40:59 |
Message-ID: | Pine.BSO.4.64.0712062135120.2548@leary.csoft.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2007-12-07 11:58:25 | Re: BUG #3806: PreparedStatement.setString(String) throws exception |
Previous Message | Tom Lane | 2007-12-07 02:19:39 | Re: [HACKERS] BUG #3799: csvlog skips some logs |