On 4/18/22 07:34, Ram Pratap Maurya wrote:
@font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;}@font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;}p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0cm; margin-bottom:.0001pt; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-fareast-language:EN-US;}a:link, span.MsoHyperlink {mso-style-priority:99; color:#0563C1; text-decoration:underline;}a:visited, span.MsoHyperlinkFollowed {mso-style-priority:99; color:#954F72; text-decoration:underline;}span.EmailStyle17 {mso-style-type:personal-compose; font-family:"Calibri","sans-serif"; color:windowtext;}.MsoChpDefault {mso-style-type:export-only; font-family:"Calibri","sans-serif"; mso-fareast-language:EN-US;}div.WordSection1 {page:WordSection1;}Hi Support,
We have upgraded postgresql DB from version 11 to 13 . after upgrade to 13 huge archive log generate in system .
Before upgrade per day 120GB to 150 GB log generated but after upgrade per day approx. 250 to 300 GB log generated.
Can you please suggest why huge archive log generated after upgrade there any configure setting or this is Postgresql-13 behaviour.
Postgresql-13 Postgresql conf file attached for your references.
Regards,
Ram Pratap.
Have you checked what's in those WAL archives? You can do that with pg_waldump. My guess would be that your vacuum is probably more active than in the version 11. However, that's just a guess. You can also turn on WAL compression. Be aware that compression will reduce disk consumption at the expense of CPU consumption.
Regards
--
Mladen Gogala
Database Consultant
Tel: (347) 321-1217
https://dbwhisperer.wordpress.com
