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 1la13x-00044T-0b for pgsql-novice@arkaria.postgresql.org; Fri, 23 Apr 2021 19:02:01 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1la13v-0004Lc-VZ for pgsql-novice@arkaria.postgresql.org; Fri, 23 Apr 2021 19:01:59 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1la0rL-0006N9-6V for pgsql-novice@lists.postgresql.org; Fri, 23 Apr 2021 18:48:59 +0000 Received: from mail-vk1-xa33.google.com ([2607:f8b0:4864:20::a33]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1la0rE-0008WS-TR for pgsql-novice@lists.postgresql.org; Fri, 23 Apr 2021 18:48:58 +0000 Received: by mail-vk1-xa33.google.com with SMTP id o17so10800104vko.8 for ; Fri, 23 Apr 2021 11:48:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=m4J5DWP/7gAQM/sLJSY98JaC3bm043L8jHySiFOVnL8=; b=Ay0YIfjejqWHDEGYmsEpf7wib+xTx80rcIsenXs4cCUVf96B+gqX3m6pHtHMsRX8Fd oHgqvfx23N9r6Wcjwtm3V+oROo9Nz2rxTP1DH1Y+2VwDCJCjowS51Nkl99GsPp+1hhKu yvkU5A0K42FjJ7NiyqPIwJ/GrHYNFk9I27RlqVxeXF5i9U2E69fAyo/ow37Mtw/Pm662 MQpVDNGBxDHgxVlRjadMlovrYVhg3aI1qKCM9KZfEmF2L2zAep0v5XW1LqZn0BdGqBNZ P+358cLoLEfiJyVXeJvV4rhMnrqwXLHZTFWDZin+LsumyvusM5NopLdHbX9QsWgyKodX w7ZA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=m4J5DWP/7gAQM/sLJSY98JaC3bm043L8jHySiFOVnL8=; b=Bb2AfVJ+Ecpu94rb7IA1JM8z7q+42HLifvgtz+9ikye1B7tvgQf6tL1sOyH5k+Dop8 MqcuCk6MCAJzXF5f6DPr1DqouZ38Bs6zj31fzV25cplG+e06j9gcRNDi9dIjsSSk+NN+ 3B8INdGuMxT2BprFrgRy6TV4OdlzkD8j349hUNAVAVIi49wYJ/+hLtEL3+gGttN+kJtF W5S2M2vbqpkLFCWZtUh0K+RP1NS87aQu6U2d5EKpUfJNkahpZAxbzpgY+Sb3CAkPVlZW KFBJZXyMKA+NNBOhoTSlvzB9J5DSKF2YeNllUg5Ft+DNC8XeQuWYLSS2O2HaJ1sixM7x VBtg== X-Gm-Message-State: AOAM531OG7X1Mz90REEW6aaXngf4MrMdJA0YfVb12v/V+VL027GnpjAf mdRNBNd0CPITrw12RjQMVlCpVSnJ2mkPWmjdnBTCcTUGXmcq8Q== X-Google-Smtp-Source: ABdhPJwTfugxvVEbdeXHuAfUgGe9Q4b+H4VHoV3k5/h/T1pszPJQvUQoX2nfZeUW8y4tXEry68qwyPKkMlFZ8ZKvwoE= X-Received: by 2002:ac5:cde5:: with SMTP id v5mr5591401vkn.16.1619203730247; Fri, 23 Apr 2021 11:48:50 -0700 (PDT) MIME-Version: 1.0 From: Pavel Tide Date: Fri, 23 Apr 2021 20:48:39 +0200 Message-ID: Subject: suppress empty archive_command warning message To: pgsql-novice@lists.postgresql.org Content-Type: multipart/alternative; boundary="00000000000029147005c0a83fe4" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000029147005c0a83fe4 Content-Type: text/plain; charset="UTF-8" Hello everyone, Is there a way to suppress the WARNING that is thrown in PG logs if archive_mode is enabled but the archive command is empty? Maybe some configuration key which I have overlooked? Thanks! --00000000000029147005c0a83fe4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello everyone,

Is there a way to suppr= ess the WARNING that is thrown in PG logs if archive_mode is enabled but th= e archive command is empty? Maybe some configuration key which I have overl= ooked?

Thanks!
--00000000000029147005c0a83fe4--