Re: BUG #4820: PostgreSQL service won't start after using Tuning Wizard

Поиск
Список
Период
Сортировка
От Dave Page
Тема Re: BUG #4820: PostgreSQL service won't start after using Tuning Wizard
Дата
Msg-id 937d27e10905210754q761ca5ebs2524b90b6d6dfa41@mail.gmail.com
обсуждение исходный текст
Ответ на BUG #4820: PostgreSQL service won't start after using Tuning Wizard  ("Robert Walker" <r.walker@mtcworldwide.com>)
Список pgsql-bugs
On Thu, May 21, 2009 at 10:42 AM, Robert Walker
<r.walker@mtcworldwide.com> wrote:
>
> The following bug has been logged online:
>
> Bug reference: =A0 =A0 =A04820
> Logged by: =A0 =A0 =A0 =A0 =A0Robert Walker
> Email address: =A0 =A0 =A0r.walker@mtcworldwide.com
> PostgreSQL version: 8.4 beta 2
> Operating system: =A0 Windows XP SP2 32-bit
> Description: =A0 =A0 =A0 =A0PostgreSQL service won't start after using Tu=
ning Wizard
> Details:
>
> I installed PostgreSQL 8.4 Beta 2 with a completely fresh install, and th=
en
> ran the Tuning Wizard. After a simple run of the Tuning Wizard, the attem=
pt
> to start postmaster via the Windows service would time-out/fail.
>
> The problem is apparently due to the fact that the tuning wizard will add
> the "max_fsm_pages" and "max_fsm_relations" parameters to postgresql.conf,
> despite the fact that 8.4 supposedly no longer uses these parameters.
>
> If I comment out those settings, the service starts without problems.
> Perhaps those settings shouldn't be added to an 8.4 postgresql.conf by the
> wizard, otherwise new users would be alarmed by the resulting failure to
> start the server. Also, nothing in the logs in the pg_log directory was
> written that gave any clue as to why the server wouldn't start.

The current version of the wizard doesn't support 8.4. An update is
currently in qa.

--=20
Dave Page
EnterpriseDB UK:   http://www.enterprisedb.com

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

Предыдущее
От: "Robert Walker"
Дата:
Сообщение: BUG #4820: PostgreSQL service won't start after using Tuning Wizard
Следующее
От: valgog
Дата:
Сообщение: Re: BUG #4819: Ordering big tables by indexed columns is very slow.