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 1n4ye0-00060X-Im for pgsql-hackers@arkaria.postgresql.org; Wed, 05 Jan 2022 05:15:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1n4ydz-0004mO-EC for pgsql-hackers@arkaria.postgresql.org; Wed, 05 Jan 2022 05:15:27 +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 1n4ydz-0004mF-3q for pgsql-hackers@lists.postgresql.org; Wed, 05 Jan 2022 05:15:27 +0000 Received: from mail-lf1-x129.google.com ([2a00:1450:4864:20::129]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1n4ydw-00058K-LO for pgsql-hackers@lists.postgresql.org; Wed, 05 Jan 2022 05:15:26 +0000 Received: by mail-lf1-x129.google.com with SMTP id g11so86685436lfu.2 for ; Tue, 04 Jan 2022 21:15:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=HmIjhIoALPRvSSHusuRAaCkZzb6A3wcNU7MvpzqsBHY=; b=Wb6dG+AoroZClU6UMDiha+ULklkwNaAhXTBY2Gsx+WGCcB9wGdOFeVIKdRGfc2xtbE CLFDRgaigHjveqtU92z7PPXX2XA7GJ0m1TLmqXwT82ZZVPFIdpGQHKb0Jyuiq+s61Rks 51BrvND16e/tSDlZsUQTQ5BQQJuNM1dYHK+aU6AZ+m6vIP63gw7Yx7nb0R92gU/vJR9W QS1IR489OltIjGSY8Uj6S0ASn3a65oeDCW14QR2w54m+AflniNzvQXtf7By1IlU/HBAR 4vUoUJLVPQ6hXUtk3fzzJcfKHcDc7zIwDChhbeo4GuuDNgiKSH79jxr+s5VwcthtGPci QV1Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=HmIjhIoALPRvSSHusuRAaCkZzb6A3wcNU7MvpzqsBHY=; b=eUunqa9IlecVrqEuJcb4OGjo8+PMKhJK3D5w09ScJ+ql+SDmD6uFB5DwGmsxg/K1bb MTTTOVPxPDAF7Q6t0ovq1JnsS0NzikYrDJ+Wm5lH5WnvqXT+7scI3TfnXQ97mTVKZRn0 iRGFTepW4gOwjxBvgWyXL/Sa0riCq0S4v7WPvBc+KPnpcZqDs7jsn2nsiFgQol5Wsz6t sWlnJkYcX7a9Q3wIPs8FRxXXcEb33rHNtc6duiI7F3H3xfK/5ao5dG1ZcflrDD7NBCfz zfI+BQVAwRuNyzLxeJgwvRFbl3pMKE+OzU8PNevyDpZXfKhrgedqrVXsUKnvN9eCgDin lOmg== X-Gm-Message-State: AOAM533hpBxs5dk7am6Hb2J78W8PG1fka55io+BMieZKyani5NJvp1h0 QB+YBuRzmxQX3C9+GcjNtiqBslMf1PVPaQX6hL06mmDwq+I= X-Google-Smtp-Source: ABdhPJy3GdRivuQ23mecwOlef+003mx7PdocnpcQV5XuCsHxyWTmR4dMJDMwxWqfh4Po2IAPsjKsZBllcyN3XDhc4Jg= X-Received: by 2002:ac2:5297:: with SMTP id q23mr43091649lfm.192.1641359722990; Tue, 04 Jan 2022 21:15:22 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Dilip Kumar Date: Wed, 5 Jan 2022 10:45:06 +0530 Message-ID: Subject: Re: Emit "checkpoint skipped because system is idle" message at LOG level if log_checkpoints is set To: Bharath Rupireddy Cc: PostgreSQL Hackers Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, Jan 5, 2022 at 10:24 AM Bharath Rupireddy wrote: > > Hi, > > Postgres server emits a message at DEBUG1 level when it skips a > checkpoint. At times, developers might be surprised after figuring out > from server logs that there were no checkpoints happening at all > during a certain period of time when DEBUG1 messages aren't captured. > How about emitting the message at LOG level if log_checkpoints is set? > Patch attached. > > Thoughts? +1 to convert to LOG when log_checkpoints is set. -- Regards, Dilip Kumar EnterpriseDB: http://www.enterprisedb.com