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 1tNTex-00BJTA-FP for pgsql-hackers@arkaria.postgresql.org; Tue, 17 Dec 2024 09:14:31 +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 1tNTeu-00GpiO-WD for pgsql-hackers@arkaria.postgresql.org; Tue, 17 Dec 2024 09:14:30 +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 1tNTeu-00GpiA-KF for pgsql-hackers@lists.postgresql.org; Tue, 17 Dec 2024 09:14:29 +0000 Received: from mail-yw1-x112f.google.com ([2607:f8b0:4864:20::112f]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tNTet-003GPw-8n for pgsql-hackers@lists.postgresql.org; Tue, 17 Dec 2024 09:14:28 +0000 Received: by mail-yw1-x112f.google.com with SMTP id 00721157ae682-6efc58fae20so44468157b3.0 for ; Tue, 17 Dec 2024 01:14:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1734426866; x=1735031666; darn=lists.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=Kqes0+zrUtWDzIo704Bl4cpSyGVZQoYhw7ZlMimxjgA=; b=YUmT6CnD6JXbr7GFs8ybULH8FXwt5dZzPsN/65SCmOTOXa/1/JVXo/J1zswkuuCefz KEXtGovwGlgCRPdX1clwLhw5hFt23kBquS0z4GPwjDPn3udsDXoKIznTyb7qjuVrMQoR XaqkNgFfaUB3L+r9eCIgPSv0h3PegNvUA90WHCTczqD7L8bFQRjgixgxTXV7IdunRJu2 6NTa+YVEwasuuDwBIr5r+DHRr+dUePhIMGjXAJ1+5rM428NCR3LYhcjH0soDS028nD5M MJomeass03gq4CsoceKLYnWBrPDvzoPNlukiJKF/gGhn/8tG7qFEFsnwyEihY9uzanb3 OmmQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1734426866; x=1735031666; 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=Kqes0+zrUtWDzIo704Bl4cpSyGVZQoYhw7ZlMimxjgA=; b=BWNMwaANmuE6x8p8HZkH58ioQdx6orWEg+8y+ffsHI2FcMHj1V22FDPSAuiqH0uwJv 9YeIgCI+Mwh05vr3XOxkCrXMbT6YHwk2+3ItPMcj8xELsgy3RpAKsoI8O6K6pjastrgf /SUhR5Y3UktKLrmKQNnZ3BIvmuElr7B0T7GDNLwEhuz7gklHS6l13+CT+rtzR0XufYXS A18VkR+m69Eeq3l9s9ySBtMDKhGg2LM3W1k7q9hbX2HnnftT/S5Oozk8PKjsZGYmD1Nn ujjlh2nf2BUZEK1PGziD/VIU59UcuF6dgUT45ev0acMSGrDuxXe3LUOaW2mX3+DXMxP7 qwlA== X-Gm-Message-State: AOJu0Yx0YFY6/DUwR7Dmj4Gk2IjJU0d0HROjrrgSGAeFGb2TKRJhTr2P lq+rkX15q8zX4lGIWdb++7rDEATlCEb+4wW4IttFEEjZ+vnsFLm3kLSY/k+3ddsD/VmTdw8bAT4 7WCs/hiIGzsZugyXr3oGWIHFneS8= X-Gm-Gg: ASbGncv7OzqTCHJQskk0RdMcy2+zcqFvKmJmriO24L+3C9XdbCjrMtiackQQZ2zWKs5 Xwy45Ez3NlAnHFAjXK5GZUry+bUQflJLMR5zh72nPx/JemujTPRFqDFctWbrC5ThL+ZPD3lGP X-Google-Smtp-Source: AGHT+IFfT9PB9Yjd2US8e+xtw//HWVqr1OK6Dl7qXj2BiunAXlJ3mGLnngUym0+M4Q+ibyIjx+fKSyMWQLF1yReVvPo= X-Received: by 2002:a05:690c:9c0b:b0:6e3:2e50:8c0c with SMTP id 00721157ae682-6f279b9f33dmr137425217b3.41.1734426866413; Tue, 17 Dec 2024 01:14:26 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: vignesh C Date: Tue, 17 Dec 2024 14:44:15 +0530 Message-ID: Subject: Re: DOCS: pg_createsubscriber wrong link? To: Peter Smith Cc: PostgreSQL Hackers 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 Mon, 16 Dec 2024 at 02:53, Peter Smith wrote: > > On Fri, Dec 13, 2024 at 8:31=E2=80=AFPM vignesh C w= rote: > > > > On Fri, 13 Dec 2024 at 10:58, Peter Smith wrote= : > > > > > > Hi, > > > > > > While reviewing the pg_createsubscriber [1] docs I found a potentiall= y > > > wrong linkend. > > > > > > This sentence: > > > "For smaller databases, initial data synchronization is recommended." > > > > > > links to [2] ("29.4.5. Initial Data Synchronization"). > > > > > > This seems to have been deliberately changed (commit [3]) > > > > > > FROM: initial data synchronizat= ion > > > > > > TO: initial > > > data synchronization > > > > > > Although the title "Initial Data Synchronization" seems at face value > > > to be relevant, this particular link target is a sub-section of "Row > > > Filters", so I don't see why this would be the intended link from the > > > pg_createsubscriber. AFAICT, the original discussion and commit > > > message does not explain. > > > > I also felt that the link was directed to the wrong page. > > > > Thanks. > > > > Here is a new patch giving an alternate link which IMO might be more > > > appropriate. > > > > How about we change the below: > > more the time when the logical replica will be available. For small= er > > - databases, > > - initial data synchronization is recommended. > > + databases, initial data synchronization is recommended. For details= , see the > > + CREATE SUBSCRIPTION > linkend=3D"sql-createsubscription-params-with-copy-data"> > > + copy_data option. > > + > > to: > > For smaller databases, it is recommended to set up > linkend=3D"logical-replication">logical replication with > linkend=3D"sql-createsubscription-params-with-copy-data">initial data > > synchronization. > > > > Hi Vignesh. > > I took parts of your suggestion: > > - I changed the 1st sentence's wording as suggested. > - I included a "logical replication" link as suggested, but I put it > earlier, where it was first mentioned on this page. > - I kept my 2nd sentence with the "copy_data" link as-is. That's > because if this docs page was in hardcopy format, doing it your way > the reader would have no clue about the link target. > > Please see patch v2. Thanks for the updated version. The v2 version patch looks great and applies cleanly to both the HEAD and PG17 branches. Regards, Vignesh