From: | Rodrigo Gonzalez <rjgonzale(at)estrads(dot)com(dot)ar> |
---|---|
To: | Tomas Vondra <tv(at)fuzzy(dot)cz> |
Cc: | BK <bero(at)artsuici(dot)de>, 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:55:55 |
Message-ID: | 4ED6601B.1080102@estrads.com.ar |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 11/30/2011 01:43 PM, Tomas Vondra wrote:
> 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?
Or maybe you have an included file after that that is hiding it?
Check for include directives in your configuration
>
> Tomas
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Reid Thompson | 2011-11-30 17:30:14 | Re: Is this safe to perform on PostgreSQL 8.3.7 -> Resize a column in a PostgreSQL table without changing data |
Previous Message | Tomas Vondra | 2011-11-30 16:43:05 | Re: Strange problem with turning WAL archiving on |