Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oUnz4-0007h7-MH for pgsql-hackers@arkaria.postgresql.org; Sun, 04 Sep 2022 11:40:14 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oUny4-0007WN-Kl for pgsql-hackers@arkaria.postgresql.org; Sun, 04 Sep 2022 11:39:12 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oUny4-0007VP-A1 for pgsql-hackers@lists.postgresql.org; Sun, 04 Sep 2022 11:39:12 +0000 Received: from mail-yb1-xb31.google.com ([2607:f8b0:4864:20::b31]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1oUnxy-0000xK-MZ for pgsql-hackers@lists.postgresql.org; Sun, 04 Sep 2022 11:39:11 +0000 Received: by mail-yb1-xb31.google.com with SMTP id c9so9244917ybf.5 for ; Sun, 04 Sep 2022 04:39:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=YmdqJAIF9Qu8WsTtL8J3U82E8qsDRlKuc04SPl16SHI=; b=bXzMHbnaPXrH3MVbVBk+RxQAx3GbVsaKLwiQ4deV4wY9sRxPSbWdMPHmV5bRutX45a pd+43pkue525eO/9pec47XigvKoG4IYWs7wFWMFDDg2dJWjwlcC8BjYDxM+EH/1nr/5c F50468n7qO69Ssz7FxrkAWapzQKG2ypswj9S87nOz7VTxHiWZljxgsZje73eZI218g2q 8Mp8b5WHvgq9YSNIpABOmhIQpZY8BiZbEwP+80d7Awt6tuPr21m/p+nGpmRJAHmkTuHW hUsZDjFWspHvSKki2LirQG8S6aW9QID5dUnIIOfrWViHDXKWqXa00d19LmkdjLBjtaCU wKJw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=YmdqJAIF9Qu8WsTtL8J3U82E8qsDRlKuc04SPl16SHI=; b=B10v2ietUqw++sCMt83MDsXSa+LqT/Xn1m4e+pTKOropt75gCj3SiZAgs59BW5hqYN QDI4osZhMN0TnZRl8KBYaL6k5cZmRDeoj/MA3JplO5/l7YPgleGTmkl6Q6crdvTi3xSn o1Yo5PxvZ64HrPq4BvoBv5Qv0TPwvvZPLmHa+joj+zlnluWYcPkebuy+w8xqOO0PSc/o zOjknz7epM330PsJTBm4CP7hDzmL5mA3u6YKEUPYTi7xyXJxqWseC98nIxw4zuEiDN3z PUJaovEvNR640+tRBVIJKnMO7ldvvvS/qFxgKHLaY4dVmRnbaHJZI7UrANaui6YbFl7G HkTQ== X-Gm-Message-State: ACgBeo2D9SZ1PI3Gb/HVyl4+s3X5wYMKNG8n/ckIVnAA85voZeMyuJmg 4PxoRVu6/g+ZQl6JtK4jB1rD6kCN3BpXYD4aOm4= X-Google-Smtp-Source: AA6agR6MXHduh5wVByhEaw8KANmSF2aJA6KtHag5Ue3e+WmxOr8pGdNtl0VicXvfZXUj5QXLzvWZvxaKKKwIMzCpjpg= X-Received: by 2002:a05:6902:1243:b0:696:717b:81be with SMTP id t3-20020a056902124300b00696717b81bemr29887672ybu.170.1662291545700; Sun, 04 Sep 2022 04:39:05 -0700 (PDT) MIME-Version: 1.0 References: <20220904081821.bck6q2j6gfp3p2im@alvherre.pgsql> In-Reply-To: <20220904081821.bck6q2j6gfp3p2im@alvherre.pgsql> From: Amit Kapila Date: Sun, 4 Sep 2022 17:08:55 +0530 Message-ID: Subject: Re: pgsql: Add ALTER SUBSCRIPTION ... SKIP. To: Alvaro Herrera Cc: Amit Kapila , Masahiko Sawada , pgsql-hackers@lists.postgresql.org Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Sun, Sep 4, 2022 at 1:48 PM Alvaro Herrera wrote: > > On 2022-Mar-22, Amit Kapila wrote: > > > Add ALTER SUBSCRIPTION ... SKIP. > > There are two messages here that seem oddly worded. > > msgid "start skipping logical replication transaction finished at %X/%X" > msgid "done skipping logical replication transaction finished at %X/%X" > > Two complaints here. First, the phrases "start / finished" and "done / > finished" look very strange. It took me a while to realize that > "finished" refers to the LSN, not to the skipping operation. Do we ever > talk about a transaction "finished at XYZ" as opposed to a transaction > whose LSN is XYZ? (This became particularly strange when I realized > that the LSN might come from a PREPARE.) > The reason to add "finished at ..." was to be explicit about whether it is a starting LSN or an end LSN of a transaction. We do have such differentiation in ReorderBufferTXN (first_lsn ... end_lsn). > Second, "logical replication transaction". Is it not a regular > transaction that we happen to be processing via logical replication? > > I think they should say something like > > "logical replication starts skipping transaction with LSN %X/%X" > "logical replication completed skipping transaction with LSN %X/%X" > This looks better to me. If you find the above argument to differentiate between the start and end LSN convincing then we can think of replacing "with" in the above messages with "finished at". I see your point related to using "finished at" for PREPARE may not be a good idea but I don't have better ideas for the same. -- With Regards, Amit Kapila.