Re: Strange problem with turning WAL archiving on

From: "Tomas Vondra" <tv(at)fuzzy(dot)cz>
To: "BK" <bero(at)artsuici(dot)de>
Cc: "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at>, pgsql-general(at)postgresql(dot)org
Subject: Re: Strange problem with turning WAL archiving on
Date: 2011-11-30 16:43:05
Message-ID: fd286dcc4038ba84a5bbc3b6dfef79ee.squirrel@sq.gransy.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 30 Listopad 2011, 17:23, BK wrote:
> Hi Albe,
>
> On Nov 30, 2011, at 2:31 PM, Albe Laurenz wrote:
>> Verify the current setting with
>>
>> SELECT setting, source, boot_val, reset_val,
>> sourcefile, sourceline
>> FROM pg_settings WHERE name = 'wal_level';
>>
>> If the setting is not right (which is likely the case), try to find out
>> the cause.
>
> This query shows that the settings are still on minimal. Strange. As I can
> see there is just one postgresql.conf file (in the data directory) of the
> 9.1 installation. Everything is changed inside it according to the specs.
> Wal_level is on archive. I even tried renaming the file, to see if when I
> reboot PostgreSQL I would get an error. I got an error and therefor it is
> the .conf that the DBMS uses.

Silly idea - the wal_level option is commented out by default. Are you
sure you've removed the '#' at the beginning?

Tomas

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Rodrigo Gonzalez 2011-11-30 16:55:55 Re: Strange problem with turning WAL archiving on
Previous Message Edson Richter 2011-11-30 16:41:52 Re: PostgreSQL 9.0 and asynchronous replication through VPN