BK wrote:
[server complains that wal_level is not set correctly]
>> Did you change the correct postgresql.conf?
>> Are there more than one lines for wal_level in the file
>> (try "grep wal_level postgresql.conf")?
>
> I tried greping, there is just one nstance of it and is set on
archive.
>
> Any
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
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
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
> t
BK wrote:
> I've spent a couple of hours trying some WAL archiving functionality
on PostgrSQL 9.1 (running on Mac
> OS X). I turned on all the needed options as specified in the
documentation:
>
> wal_level = archive
> archive_mode = on
> archive_command='test ! -f /Volumes/baza/%f && cp %p /Volum
