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 1rRsdD-009uN7-Gn for pgsql-hackers@arkaria.postgresql.org; Mon, 22 Jan 2024 11:38:24 +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 1rRscE-003Z7S-LQ for pgsql-hackers@arkaria.postgresql.org; Mon, 22 Jan 2024 11:37:22 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rRscE-003Z7K-CE for pgsql-hackers@lists.postgresql.org; Mon, 22 Jan 2024 11:37:22 +0000 Received: from mail-lj1-x22d.google.com ([2a00:1450:4864:20::22d]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rRscB-002mR9-VB for pgsql-hackers@postgresql.org; Mon, 22 Jan 2024 11:37:21 +0000 Received: by mail-lj1-x22d.google.com with SMTP id 38308e7fff4ca-2ccec119587so37030711fa.0 for ; Mon, 22 Jan 2024 03:37:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1705923438; x=1706528238; darn=postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=wRUkMHKFeW0E3hQB3RL5zjMQ8LVBO1KYvT5hW+XNAJ0=; b=dkbQpLQ5zzMcOgDZesyVyb1ooHOgTpnhSDnTBEvwNf4jxOkNlfvqdpbY0Zr+a8/fd2 SVFPU4zpbe9DLAMXsci+/xn715VA+2q7kyvSxDwcfq48oUhlJ6mO7avxF5edkYBuQPG2 yrHJWfTgvlFEKQIaMnlk+e/JlpQ4RkbVMmRWHRvCQmtT3F5B9EbDxxlbxYrRKlDVbEeY Y5n9TxG515tp4+A0ulSWhd8T2yVIEE2lAv7Ue7edPVl8LGL2q8YTb8knEvm7l6tD4eNl JVhYPCrUnrB9ybfxz2WsF/S5ga/SLJAwHOOKDY+sjzA+pvGSZvZ1thBndI5Z0d5SQvdc p8vA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1705923438; x=1706528238; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=wRUkMHKFeW0E3hQB3RL5zjMQ8LVBO1KYvT5hW+XNAJ0=; b=iT1Kcw7aJUjyi4kpoLRwDoD5qDeK4lGZ7RqKObJwQMTv1VweSxdoOFieZxa++9RWJ2 +cZinndbxcBKu71qrLbWcR29oVNnkEB3ksrgI5kVj2wpt0ujHqrrndYKcpNGsLpctXPG 8D1SFv+hLgCNbM6eWyZlFTmBpa5lgHJRUCUHD8tVpCHRZ8Qwj2SLtJDRK0bdMnFUsaBO Jy0i+SpBMY1tiG+bxeVV7AlOFB8nXVUnR59Z/1d9hWABCQShVXWTI7RNohQEFwnYUEOf EpVCIVmD7dGU8v36xgeBh7bMNFP6oa2xkiMt4aHvrjY+nD5MHATxAJbmyHWuoMrHDtfe nA/Q== X-Gm-Message-State: AOJu0YxoNNp03WDk9kn0j90+BDzziECK8AAXKytJVlHb7+ZT4g/pP1ud RSxOBOaSrwUiLaRy9qr3f3Vz7d71DFElMVgnFcCxYx3KRYSntqTk6dg5wZvY3VmVlDBT/eWgT9b lTf5NhmB2yReZmw7wssi4FiwR7x8= X-Google-Smtp-Source: AGHT+IGbJHN2IzG3ZbZLglebGt4KE8g5CUCQ3T+HnvW8Get5EzI7eQhFhUdzCc7qFZZsfahwAgyTy0Xxee8RNx15FlI= X-Received: by 2002:a2e:5c89:0:b0:2cc:f9e1:f9ed with SMTP id q131-20020a2e5c89000000b002ccf9e1f9edmr1889405ljb.105.1705923438114; Mon, 22 Jan 2024 03:37:18 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: shveta malik Date: Mon, 22 Jan 2024 17:07:05 +0530 Message-ID: Subject: Re: Synchronizing slots from primary to standby To: Peter Smith Cc: Bertrand Drouvot , Masahiko Sawada , Amit Kapila , "Zhijie Hou (Fujitsu)" , Dilip Kumar , Nisha Moond , "Hayato Kuroda (Fujitsu)" , Bharath Rupireddy , Peter Eisentraut , Bruce Momjian , Ashutosh Sharma , Andres Freund , pgsql-hackers , Ajin Cherian , Alvaro Herrera , shveta malik Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, Jan 19, 2024 at 11:48=E2=80=AFAM Peter Smith wrote: > > Here are some review comments for patch v63-0003. Thanks Peter. I have addressed all in v65. > > 4b. > It was a bit different when there were ERRORs but now they are LOGs > somehow it seems wrong for this function to say what the *caller* will > do. Maybe you can rewrite all the errmsg so the don't say "skipping" > but they just say "bad configuration for slot synchronization" > > If valid is false then you can LOG "skipping" at the caller... I have made this change but now in the log file we see 3 logs like below, does it seem apt? Was the earlier one better where we get the info in 2 lines? [34416] LOG: bad configuration for slot synchronization [34416] HINT: hot_standby_feedback must be enabled. [34416] LOG: skipping slot synchronization thanks Shveta