Re: wal_level not changing

From: Sumeet Shukla <sumeet(dot)k(dot)shukla(at)gmail(dot)com>
To: Vasilis Ventirozos <v(dot)ventirozos(at)gmail(dot)com>
Cc: pgsql-admin <pgsql-admin(at)postgresql(dot)org>
Subject: Re: wal_level not changing
Date: 2017-09-04 16:08:57
Message-ID: CABUL1375oyphOFnUfPeVPQO3rYmq9BLLzFOebmpL92TRSdHQBQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

I restarted the service using systemctl and now the status shows green but
the problem persists.

Thanks & Regards,
Sumeet Shukla

On Mon, Sep 4, 2017 at 9:28 PM, Sumeet Shukla <sumeet(dot)k(dot)shukla(at)gmail(dot)com>
wrote:

> Tried but does not work.
>
> I see below output when I check the status of the service.
>
> systemctl status postgresql-9.6
>
> *●* postgresql-9.6.service - PostgreSQL 9.6 database server
>
> Loaded: loaded (/usr/lib/systemd/system/postgresql-9.6.service;
> enabled; vendor preset: disabled)
>
> Active: *failed* (Result: exit-code) since Mon 2017-09-04 11:25:42
> EDT; 27min ago
>
> Process: 28093 ExecStop=/opt/postgresql/9.6/bin/pg_ctl stop -m fast -w
> -D /data/9.6/data *(code=exited, status=1/FAILURE)*
>
> Process: 28052 ExecStart=/opt/postgresql/9.6/bin/pg_ctl start -w -t
> ${TimeoutSec} -D /data/9.6/data -l /data/9.6/data/pg_log/startup.log
> (code=exited, status=0/SUCCESS)
>
> Main PID: 28054 (code=exited, status=0/SUCCESS)
>
>
> Sep 04 11:25:36 ashprmlpdb-p05 systemd[1]: Starting PostgreSQL 9.6
> database server...
>
> Sep 04 11:25:36 ashprmlpdb-p05 systemd[1]: Started PostgreSQL 9.6 database
> server.
>
> Sep 04 11:25:42 ashprmlpdb-p05 systemd[1]: *postgresql-9.6.service:
> control process exited, code=exited status=1*
>
> Sep 04 11:25:42 ashprmlpdb-p05 systemd[1]: *Unit postgresql-9.6.service
> entered failed state.*
>
> Sep 04 11:25:42 ashprmlpdb-p05 systemd[1]: *postgresql-9.6.service
> failed.*
>
>
> Thanks & Regards,
> Sumeet Shukla
>
>
> On Mon, Sep 4, 2017 at 9:20 PM, Vasilis Ventirozos <v(dot)ventirozos(at)gmail(dot)com
> > wrote:
>
>> try ALTER SYSTEM set wal_level = 'minimal';
>> and then restart , just make sure that archiving is disabled first.
>>
>> Vasilis Ventirozos
>>
>>
>> On 4 Sep 2017, at 18:42, Sumeet Shukla <sumeet(dot)k(dot)shukla(at)gmail(dot)com> wrote:
>>
>>
>> Hi,
>>
>> update pg_settings set reset_val='minimal' where name='wal_level';
>>
>> ERROR: parameter "wal_level" cannot be changed without restarting the
>> server
>>
>>
>> set wal_level='minimal';
>>
>> ERROR: parameter "wal_level" cannot be changed without restarting the
>> server
>>
>>
>> update pg_settings set setting='minimal' where name='wal_level';
>>
>> ERROR: parameter "wal_level" cannot be changed without restarting the
>> server
>>
>>
>> Even after restarting and reloading the server multiple times the setting
>> does not update and remains as below:
>>
>> show wal_level;
>>
>> +-----------+
>>
>> | wal_level |
>>
>> +-----------+
>>
>> | replica |
>>
>> +-----------+
>>
>>
>>
>> Thanks & Regards,
>> Sumeet Shukla
>>
>>
>>
>

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Vasilis Ventirozos 2017-09-04 16:16:06 Re: wal_level not changing
Previous Message tirveni yadav 2017-09-04 16:08:19 Re: New to postgreSQL