From: | merina ghoghwani <merinaghoghwani(at)gmail(dot)com> |
---|---|
To: | pavan95 <pavan(dot)postgresdba(at)gmail(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Limiting the no. of logs file generated by postgreSQL |
Date: | 2018-02-15 13:24:30 |
Message-ID: | CAKoQ0XEJLafsm+vtiZ1UHiJVAoyXpLx43bNiJmyZyF2ehSGAew@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi Pavan,
At the time of the outage, the logs were off. I am assuming, the logs
increased because I am using replication.
Below is the postgresql.conf,
log_destination = 'stderr'
logging_collector = on
log_filename = 'postgresql-%a.log'
log_statement = 'none'
All other parameters are default values.
On Thu, Feb 15, 2018 at 6:09 PM, pavan95 <pavan(dot)postgresdba(at)gmail(dot)com>
wrote:
> Hello Merina,
>
> Firstly, did you observe the log files like what is getting logged? In
> case
> check whether it is logging all the statements ran on the server..!
>
> This will be caused because of the parameter "log_statements".
>
> What is the value of 'log_statements ' set in your configuration file
> 'postgresql.conf'?
>
> I think because of this parameters this is increasing the size of the log
> files. You can cross verify over that area.
>
> For further analysis provide the snap of Error Reporting and Logging
> parameters.!
>
> Regards,
> Pavan.
>
>
>
> --
> Sent from: http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.
> html
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | pavan95 | 2018-02-15 13:40:13 | Re: Limiting the no. of logs file generated by postgreSQL |
Previous Message | pavan95 | 2018-02-15 12:39:47 | Re: Limiting the no. of logs file generated by postgreSQL |