Yes so many wals are continuing to be produced.
Deleting the wals after a backup of the database.
Yes archiving mode is on. And the warning message in log file is
" checkpoints are frequently occurring (1second apart). Consider increasing checkpoint_segements parameter".
My doubt is previously the same are the parameters which are reflected as of now. Then what is the point in considering altering those values. Correct me if I am wrong.
Regards,
Pavan
On Jan 23, 2018 7:47 PM, "Andreas Kretschmer" <andreas@xxxxxxxxxxxxxxx> wrote:
Will so many wals continue to be produced?
Am 23.01.2018 um 12:51 schrieb pavan95:
Hi Andreas,
Yes I'm facing problem because of this huge WAL(archive log) generation. As
it is seriously consuming a lot of disk space almost close to 50GB per day
even if the DML's don't have that impact in this WAL generation.
Previously the archive_log size is nearly 2 to 3 GB a day. Now with the same
set of DML's how is it being generated to 50GB is my burning doubt.
Don't delete wal's!
I just wanted to know how to stabilize this issue, as checking and deleting
the archive logs on hourly basis is not a good idea.
have you set archive_mode to on and defined an archive_command? Wal-files will be reused after 2 checkpoints.
Finally, I'm looking how to reduce this back to normal. Thanks in Advance.
Is there something in the logs?
Regards, Andreas
--
2ndQuadrant - The PostgreSQL Support Company.
www.2ndQuadrant.com
