Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ngWqh-0005He-VN for pgsql-admin@arkaria.postgresql.org; Mon, 18 Apr 2022 19:15:48 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ngWqg-0000Vc-OU for pgsql-admin@arkaria.postgresql.org; Mon, 18 Apr 2022 19:15:46 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ngWqg-0000VE-8B for pgsql-admin@lists.postgresql.org; Mon, 18 Apr 2022 19:15:46 +0000 Received: from mail-wr1-x430.google.com ([2a00:1450:4864:20::430]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1ngWqd-0007Si-Ne for pgsql-admin@lists.postgresql.org; Mon, 18 Apr 2022 19:15:45 +0000 Received: by mail-wr1-x430.google.com with SMTP id w4so19591915wrg.12 for ; Mon, 18 Apr 2022 12:15:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:to:subject:thread-topic:thread-index:date:message-id :references:in-reply-to:accept-language:content-language :mime-version; bh=d5KT/n+XRm8nzU7vfEgxGTriwuFgQhmvFaQAEXtXLM0=; b=jedS+RGUt6v02/zqr8M195qm7Xz4WpEuhS3t+xF3AD1ourcBt7RtnzJtJHPzeWA/JJ wJSw5wLy91j9DmKEEBFXjPnTM4Y/SmdRrSm0bDbLbr0kdXHN4oFopBiQwqbMntot66gJ nt7UuANzVxbSO1OcGebP/dtMnTbDsoSaJPookb6jCsuJ9S56o1G8TE49b19DHXvxKO6A zKq3j7tZiGvCS9m7XOigBTWyDf154Iv/B7NGzD5NNuAQu2YyhT/BkLYppaqx7LpHSfDH P/yJQPvFvjPLt7c0KTo3jr0ibt3i1G0VqDUHUoKuqRsRJNxk/Q2oMavS0pU5UWTduEqm oE0g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:subject:thread-topic:thread-index:date :message-id:references:in-reply-to:accept-language:content-language :mime-version; bh=d5KT/n+XRm8nzU7vfEgxGTriwuFgQhmvFaQAEXtXLM0=; b=nEWf7iSaMcSOTAXyxCEUqdRkl9/6JA3SHkD8olJ162huFaUPoi9M9FFUgZfeG3y6mE oxVZJc7CVFaWS5FqCif0M1iP2ecNIoJMUK1ZA0wET8OCKHP6Kvmi/3kXM9aJfYayVjmQ SwLO26X6I92214jCg+6DMH0ED1kxZ8cClILPo2oKTZQQ9Vr62tZ4cLu+HdOKDl4XhDY3 lPL40Qn1ZuBMKqx8cBzE5yIte1lFwO0+mx8taJqyveT2fn1M+UjZ5UwEULlD/WFOOJLa zhLDy/yfQZ4cwPEYwuJQXPFkyWUitdFrMQbtVG3saievWMDlNxZnyNZDxiz/IWFIEJB/ 0gQw== X-Gm-Message-State: AOAM532pUXEVlXHvHxbrUoe4R1+hsDbIpq9BW9ZFkO29P61m2bZXRHI5 s2EgATceo+4yUfbReLsXFDyyVaNCEXU= X-Google-Smtp-Source: ABdhPJwIYL8tDljPbkW5dMM2ZCbPAX88pkYCEdl19ljfu1SeTcsa5fbC6Tc3iQr9/Tmmv9RsMqc41A== X-Received: by 2002:a5d:47a1:0:b0:20a:9d5e:e1cd with SMTP id 1-20020a5d47a1000000b0020a9d5ee1cdmr3028591wrb.428.1650309342314; Mon, 18 Apr 2022 12:15:42 -0700 (PDT) Received: from CWXP123MB3959.GBRP123.PROD.OUTLOOK.COM ([52.97.253.85]) by smtp.gmail.com with ESMTPSA id r3-20020a1c2b03000000b00392a3e6280bsm240634wmr.8.2022.04.18.12.15.41 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 18 Apr 2022 12:15:41 -0700 (PDT) From: Clive Swan To: Holger Jakobs , "pgsql-admin@lists.postgresql.org" Subject: Re: Huge archive log generate in Postgresql-13 Thread-Topic: Huge archive log generate in Postgresql-13 Thread-Index: AdhTFtcEyGI0ruNgRta+FOh1rB9IDgAAz8XgAADKLAAADs7bDw== X-MS-Exchange-MessageSentRepresentingType: 1 Date: Mon, 18 Apr 2022 19:15:38 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-GB X-MS-Has-Attach: X-MS-Exchange-Organization-SCL: -1 X-MS-TNEF-Correlator: X-MS-Exchange-Organization-RecordReviewCfmType: 0 Content-Type: multipart/alternative; boundary="_000_CWXP123MB3959D7C4AB99BE0D1D6F38F4A0F39CWXP123MB3959GBRP_" MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --_000_CWXP123MB3959D7C4AB99BE0D1D6F38F4A0F39CWXP123MB3959GBRP_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Grenting, Is your logging set to high verbosity?? Usually use high verbosity for debugging, then change to low verbosity. Clive ________________________________ From: Holger Jakobs Sent: Monday, 18 April 2022, 13:10 To: pgsql-admin@lists.postgresql.org Subject: Re: Huge archive log generate in Postgresql-13 wal_level =3D hot_standby # minimal, replica, or logical # (change requires restart) Set wal_level to one of the allowed values. It's possible that your value g= ets interpreted as logical, thus creating larger wal entries. Am 18.04.22 um 13:47 schrieb Ram Pratap Maurya: 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. -- Holger Jakobs, Bergisch Gladbach, Tel. +49-178-9759012 --_000_CWXP123MB3959D7C4AB99BE0D1D6F38F4A0F39CWXP123MB3959GBRP_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Grenting,
Is your logging set to high verbosity??

Usually use high verbosity for debugging, then change to low verbosity.&nbs= p;

Clive

From:= Holger Jakobs <holger@jakobs.com>
Sent: Monday, 18 April 2022, 13:10
To: pgsql-admin@lists.postgresql.org <pgsql-admin@lists= .postgresql.org>
Subject: Re: Huge archive log generate in Postgresql-13


wal_level =3D hot_standby         &nb= sp;  # minimal, replica, or logical
               =     # (change requires restart)

Set wal_level to one of the allowed values. It's possible that your valu= e gets interpreted as logical, thus creating larger wal entries.

Am 18.04.22 um 13:47 schrieb Ram Pratap Maur= ya:

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 upgrad= e per day approx. 250 to 300 GB log generated.

Can you please suggest why huge archive log generated after upgrade  t= here any configure setting or this is Postgresql-13 behaviour.

 

Postgresql-13 Postgresql conf file attached for your references.

 

 

Regards,

Ram Pratap.

 

-- =0A=
Holger Jakobs, Bergisch Gladbach, Tel. +49-178-9759012

--_000_CWXP123MB3959D7C4AB99BE0D1D6F38F4A0F39CWXP123MB3959GBRP_--