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 1t41Hh-00FyV0-F6 for pgsql-admin@arkaria.postgresql.org; Thu, 24 Oct 2024 17:06:05 +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 1t41Hf-005kD6-Qp for pgsql-admin@arkaria.postgresql.org; Thu, 24 Oct 2024 17:06:04 +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 1t41Hf-005kCx-FT for pgsql-admin@lists.postgresql.org; Thu, 24 Oct 2024 17:06:03 +0000 Received: from mail-ej1-x632.google.com ([2a00:1450:4864:20::632]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1t41Hd-002ljS-PQ for pgsql-admin@lists.postgresql.org; Thu, 24 Oct 2024 17:06:03 +0000 Received: by mail-ej1-x632.google.com with SMTP id a640c23a62f3a-a99f629a7aaso191690866b.1 for ; Thu, 24 Oct 2024 10:06:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1729789560; x=1730394360; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=UmMhaMnLm24bhhwmQX60bwuUvP6IggFHq8fM/nT0T5w=; b=jP8/CwMwt2oMGGJIZ2xQHDcdYJnhP6R7dGrYV3z+QAtjEVI5xwHylQEGkyvRYwVGNp cZAEaZI9kF0Ze9pIEHIJgzFkVbepIprSEyFmm3TPImwUGfaaxhuuCs8jetMRUjrxOSS/ Z5lVvFbM0rz8TKY3yA+r3PSXmkO3KnonipOgm8MmfOM3YlxI+xBBupGqjnB+wUYkm1Xf osAB3dGs/etY4B63HGO3dOmRPoMD4TGtpGmDFs7dXCx1YbSx4RrbfIQaTqUHqyb93ezG 1xEJIrf8Sm9WipHzqncyBG1ztTMeziZmngcChC6SUuOAtdlzlQfFz7Zn6Jf9W9vCZgHB CQLg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1729789560; x=1730394360; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=UmMhaMnLm24bhhwmQX60bwuUvP6IggFHq8fM/nT0T5w=; b=lTX1IGqABUk0oVKCTg4cvcrQKPlHNlnCkt7TXCMYD1z0lM/pAQZnGN9j1CPxJbajdm JzvrELjWJtYqf28OsfGiyMNefmZAyQnMfTRKQQOkr5wbJO/2jEdKg2lWThoKorit9a3G 6S5RL/GaNzJAajsyPUg6YPFwNg1VZu7/PF3g/Jy0veqU4hAMktZe+9nh8AalSRrClAUa s4wPvEedfQwvBvY98aJU/mq3Zf8n4ASDahrJTUZetcNwcG2bHAElyUl5WQwO3nb8s1IM FM5c4MMYMCaz18zgkAr5fsSDt3K7vrdEN2pA0rtOEbM62reuBZXbmMxC5QhYkaWX4CaX 5m8w== X-Gm-Message-State: AOJu0YyaIhQyHJPVe6IyHFWfoxb0fYsdKmWgGQdV3w2VVbAjBd+H1XaR 9ijb/vu52+bgIOm2a8vTEI/MuY03c1DJz8tap5mgDMOjYZ4wxZcZ52AT5tAgUH5xIylMb1fGi7T mY5qhMM6tvjjsXQmp9CX3L9d87I5r/mji X-Google-Smtp-Source: AGHT+IHwojRdOfUdzGCKs/n+yq+w1htCtFGfxNx4t+JyeOln/2nHbmysNieDMV3dHqHyDHAOixwdW8gouh3cgLI2Zww= X-Received: by 2002:a17:907:94cd:b0:a99:5587:2a1f with SMTP id a640c23a62f3a-a9ad19c145emr338059566b.15.1729789560518; Thu, 24 Oct 2024 10:06:00 -0700 (PDT) MIME-Version: 1.0 From: Nikhil Shetty Date: Thu, 24 Oct 2024 22:35:49 +0530 Message-ID: Subject: Will there be data loss between slot syncronisation To: Pgsql-admin Content-Type: multipart/alternative; boundary="0000000000004a7e5406253c0451" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000004a7e5406253c0451 Content-Type: text/plain; charset="UTF-8" Hi Team, As per documentation for sync_replication_slots: The nap time of the worker is tuned according to the activity on the primary. The slot sync worker waits for some time before the next synchronization, with the duration varying based on whether any slots were updated during the last cycle. What happens if there is a long period where the standby slot is not synced and there is autofailover? Will there be a data loss? Thanks, Nikhil --0000000000004a7e5406253c0451 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Team,

As per documentation for=C2=A0= sync_replication_slo= ts:

The=C2=A0nap=C2=A0time=C2=A0of=C2=A0the=C2=A0worker=C2=A0is= =C2=A0tuned=C2=A0according=C2=A0to=C2=A0the=C2=A0activity=C2=A0on=C2=A0the<= /span>
primary.=C2=A0The=C2=A0slot=C2=A0syn= c=C2=A0worker=C2=A0waits=C2=A0for=C2=A0some=C2=A0time=C2=A0before=C2=A0the= =C2=A0next
synchronization,=C2=A0wit= h=C2=A0the=C2=A0duration=C2=A0varying=C2=A0based=C2=A0on=C2=A0whether=C2=A0= any=C2=A0slots=C2=A0were

updated=C2= =A0during=C2=A0the=C2=A0last=C2=A0cycle.

What happens if th= ere is a long period where the standby slot is not synced and there is auto= failover? Will there be a data loss?

Tha= nks,
Nikhil
--0000000000004a7e5406253c0451--