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 1tXGW8-0059rw-E1 for pgsql-hackers@arkaria.postgresql.org; Mon, 13 Jan 2025 09:13:52 +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 1tXGW5-009Evs-HM for pgsql-hackers@arkaria.postgresql.org; Mon, 13 Jan 2025 09:13:50 +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 1tXGW5-009Evk-4n for pgsql-hackers@lists.postgresql.org; Mon, 13 Jan 2025 09:13:49 +0000 Received: from mail-yb1-xb31.google.com ([2607:f8b0:4864:20::b31]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tXGW3-00093V-1x for pgsql-hackers@lists.postgresql.org; Mon, 13 Jan 2025 09:13:49 +0000 Received: by mail-yb1-xb31.google.com with SMTP id 3f1490d57ef6-e53a5ff2233so7343682276.3 for ; Mon, 13 Jan 2025 01:13:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1736759626; x=1737364426; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=X9EShapvUHqdHjAYmx2Otcy5B1Jv9Pi7XB1D46n/qu4=; b=iQx8sSru2u8fFmpewTc8o0qxQYxLRqOnhGhOK/dFNw6IEACHZzRIQ1qMBmJmvpnl3A fgyHARS3J0GbB/7pDJqYZ/fB5CnKtSx1xWdZnTVK+FGEGPesEunmUF098imwwleLRV4s CxV+EsKXYmZ8gJhtxSRhxZBGdm54w4qspgOSmngxOSqvJU+WmrO/044Mure+ZG6wkiLd gB5/heVdLVIKo+mX9CNmO0AnlmMykiLf5XVDYcvz3yv3dmwTDAchOQ9M9KXHwy73Dh6d Ot15l8ogwZl6gj9bxZ9o5jXHUdsxCfPbHbugoqCpfvQ4c8sFQvEHUpLehr6Up4miwBMN WZyQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1736759626; x=1737364426; h=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=X9EShapvUHqdHjAYmx2Otcy5B1Jv9Pi7XB1D46n/qu4=; b=mv0m3O/nstllQviA35xBWFxLkx0RFZrH+meQeNjCNpfO+0YGhiKgx3SF+GaVRP3+B9 9tFtaLwMFe06sOoCvBMcqpLg2J/mJv0M8CYRZjVbbnwJniqKqMfASyy8aPM6tceSkTMl q1cvoApVEhdBV0rkPBTqe2AjC6+QDpfnfRQ/m7Y6boaO4CVrKeS7ySMebuJ02i+ebdZj yeakONjPvCBMSDsLwkRBb4IjQRBAjykTYoHK1MhOy03UqOhxL6hZO7IX451FxJkH6W+g mHjlWCOfvc6+hf7ojuWnS8k0XKe+2ry3P+qGGUm1lqSxqYI2Wo7+tshv/8gVy0oD1ZgH +tYw== X-Forwarded-Encrypted: i=1; AJvYcCWjOQ5P9YRq+jmNScUGTOrC4lnYygiKmy2G4Dw5xuZ2bMcgQZYAyeev5/Pb33jXJvww61lyVo9KDo80gFIb@lists.postgresql.org X-Gm-Message-State: AOJu0YzcxrnnOL6hg0ShEIWwBAwRy2v9/D0ftLC+cJZ3fcK1wuvuIMmH CAAWtSs1xSF+CcUD9XLxl/HXHG516Z8gL4xnsIxjRLVIcWnSzPeIFVEhkWLzAPhZn0sWxg4jWnm En211QqEcEkV2s/03dignVOoi1p0= X-Gm-Gg: ASbGnct+YCHXrkasajJjKtMNT9zhCyeYnSVydtLPPeH+UQweeCoQQcgkeyHpDCzlYXQ AfRIDJ/A0dreVsqusnyi145l9EE5NrI+XR8GekxLh X-Google-Smtp-Source: AGHT+IHYNUi5PtRnL+14efz0sfa4AnNxorTW/2qez507+1QEpwG0KLv+OEQQKtgdx6UrAzFLKI1wFMKyPAYg43He73Q= X-Received: by 2002:a05:6902:2310:b0:e57:590c:f48d with SMTP id 3f1490d57ef6-e57590cf56cmr2480844276.2.1736759625964; Mon, 13 Jan 2025 01:13:45 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Shlok Kyal Date: Mon, 13 Jan 2025 14:43:34 +0530 X-Gm-Features: AbW1kvasKBFPmiq8NakFnkL7w6BAXI2D4EVzBMH2I_AtWwA6oVpuK5CHEjFuJKE Message-ID: Subject: Re: Documentation update of wal_retrieve_retry_interval to mention table sync worker To: vignesh C Cc: Peter Smith , 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 Mon, 13 Jan 2025 at 12:33, vignesh C wrote: > > On Mon, 6 Jan 2025 at 08:47, Peter Smith wrote: > > > > Hi Vignesh, > > > > Some review comments for your v2 patch. > > > > ====== > > doc/src/sgml/logical-replication.sgml > > > > AFAICT the only difference you made is changing: > > FROM "a special kind of apply process" > > TO "a special kind of table synchronization worker process". > > > > There is only ONE kind of tablesync process, so I think saying "a > > special kind of table synchronization worker process" seems > > misleading. I also thought maybe it is better to mention that this is > > PER table. > > > > SUGGESTION: > > ... a special table synchronization worker process per table. > > Thanks, the updated v3 version patch has the changes for the same. > Hi Vignesh, I reviewed the v3 patch. And it looks good to me. Thanks and Regards, Shlok Kyal