Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rpFC6-005nee-5r for pgsql-general@arkaria.postgresql.org; Tue, 26 Mar 2024 22:22:58 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rpFC3-006sKX-7J for pgsql-general@arkaria.postgresql.org; Tue, 26 Mar 2024 22:22:55 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rpFC2-006sKP-QW for pgsql-general@lists.postgresql.org; Tue, 26 Mar 2024 22:22:54 +0000 Received: from mail-pg1-x52b.google.com ([2607:f8b0:4864:20::52b]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rpFBw-006ecg-3X for pgsql-general@lists.postgresql.org; Tue, 26 Mar 2024 22:22:54 +0000 Received: by mail-pg1-x52b.google.com with SMTP id 41be03b00d2f7-5cfd95130c6so3381743a12.1 for ; Tue, 26 Mar 2024 15:22:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1711491765; x=1712096565; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=INLQ+ni+1lWpdVaCIsbr4VWmsp5ixHpk96KIAJWaaPA=; b=StNtJtGgDM2cN1CHFxTl/SWIH/q32mscydhk0nlXyXXmnVTDpRJSBxFV3qp5z6FeZU +UO1QenJ0WU/k7Nm2TZitM8asUHIcEOGPMVZQzi6woEnPuDHLriw9+D1v3UOeUAobAZm kl2Zn4Zgv7X6h82uGICT3vbaRilrk/+Ad++cCgFUuOyuIU0Lo0ng2PasD8F3dblscdSU Ib6Wj4DqV8cAVeVzPBcwEwEfIJ5IcJdAvZvlk5owlIHZklRCiEXY3mRjU/5ukG9sP7KT 6ZVg5FBIhQF9NJeQ8Ix2l4alDKYR6IxPHdkby6kbHHOOrL/Owgyqbcb3PDc9dENRbUy6 L5Nw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711491765; x=1712096565; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=INLQ+ni+1lWpdVaCIsbr4VWmsp5ixHpk96KIAJWaaPA=; b=FAeAr1YLNqWYkBAdsn0aOhu1Y7sHO2Vv0W6elgKAGwPjpbqv9GvMA7Qhc+M3tmCwrz cA4ac2iRM5uYIyE/AnTj8Hy3r8v9PXf/NKMZ6r8DW9fp6JkJx1hRaGZg4KwwN7frAylP 0E4z/m6h1zELx5TnL8GMjm8czLtIgkGDQvI00mS4ABKpBPdTzkylBKZTH5LxHsldXkKJ T6iotusboJJa69RV3frKNa74gAgmnG1xr10+YBnNiiHOcP2jQQ5k6uBVd/jnNNuWKheP DhYO5trKvMRdZ3oQUEyYy9Fbefk6mon/CxCagBqfQVELEGX/d0sBavWr247weT72lior xEMA== X-Gm-Message-State: AOJu0YxipRqbAG0SBJjHQ2X+hdZ8LLCBSRtaeIwovoH9yN8wR4dUjV/i 65pknNGE/daB6AnTTq4uwd+cO/l7zco+wLm05aj4+D7To+fhi+tKBZZmsRDvty20qeXvYp4mzuo HTfNm5Tvefm5gppSFBsVjmwcmZmieZC4DtPo= X-Google-Smtp-Source: AGHT+IGCdLl8lLeVCQOZfcTQ9rKIAaJiNGzmGdhxca7jg8jJY+Z0BFkOgnxOovq4XJQazeSQy2cSyx7lDKZhGzEK6AI= X-Received: by 2002:a05:6a20:7344:b0:1a3:c4ea:f38a with SMTP id v4-20020a056a20734400b001a3c4eaf38amr8390570pzc.41.1711491764926; Tue, 26 Mar 2024 15:22:44 -0700 (PDT) MIME-Version: 1.0 From: Isaac Morland Date: Tue, 26 Mar 2024 18:22:32 -0400 Message-ID: Subject: recovery.signal not being removed when recovery complete To: "pgsql-general@lists.postgresql.org" Content-Type: multipart/alternative; boundary="000000000000af47b6061497baea" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000af47b6061497baea Content-Type: text/plain; charset="UTF-8" I use a script to restore a backup to create a testing copy of the database. I set the following in postgresql.auto.conf: recovery_target = 'immediate' recovery_target_action = 'promote' In the logs I get "recovery stopping after reaching consistency" then a moment later "database system is ready to accept read-only connections", then some entries about restoring log files, then "database system is ready to accept connections". I am able to make changes (e.g. CREATE TABLE), yet recovery.signal is still present. My understanding is that recovery.signal should be removed when recovery is finished (i.e., more or less when "database system is ready to accept connections" is logged?), unless recovery_target_action is set to 'shutdown'. Any ideas? Even just confirming/denying I understand the above correctly would help. --000000000000af47b6061497baea Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I use a script to restore a backup to create a testing cop= y of the database. I set the following in=C2=A0postgresql.auto.conf:
recovery_target =3D 'immediate'
recovery_target_act= ion =3D 'promote'

In the logs I get &q= uot;recovery stopping after reaching consistency" then a moment later = "database system is ready to accept read-only connections", then = some entries about restoring log files, then "database system is ready= to accept connections".

I am able to make ch= anges (e.g. CREATE TABLE), yet recovery.signal is still present. My underst= anding is that recovery.signal should be removed when recovery is finished = (i.e., more or less when "database system is ready to accept connectio= ns" is logged?), unless=C2=A0recovery_target_action is set to 'shu= tdown'.

Any ideas? Even just confirming/denyin= g I understand the above correctly would help.
--000000000000af47b6061497baea--