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 1ugVAH-00429h-5d for pgsql-hackers@arkaria.postgresql.org; Mon, 28 Jul 2025 21:13:45 +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 1ugVAG-00B9Tz-9V for pgsql-hackers@arkaria.postgresql.org; Mon, 28 Jul 2025 21:13:44 +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 1ugVAF-00B9Tr-Uw for pgsql-hackers@lists.postgresql.org; Mon, 28 Jul 2025 21:13:44 +0000 Received: from mail-oi1-x22e.google.com ([2607:f8b0:4864:20::22e]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1ugVAD-001MjW-0l for pgsql-hackers@lists.postgresql.org; Mon, 28 Jul 2025 21:13:43 +0000 Received: by mail-oi1-x22e.google.com with SMTP id 5614622812f47-41b6561d3e6so2958828b6e.1 for ; Mon, 28 Jul 2025 14:13:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mixrank.com; s=googledamrudlacagu; t=1753737220; x=1754342020; 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=ezL2HT4b3NmDh/7FJ9thrkjKfd0k0fuvaqD/KBu7IHo=; b=SmDvurWXh8PWURRTRxqEHZAPLbZNZLOlS6CQnQ3qL+SOIUbSF5Fp6koerm9axua9sx pUmgAK1kMChcHQ7fZcDNrcCBqJjh3xHy/ptxq0SYOQiEVaOmIuak0R9wgWg+adBd56zJ OUdLyrbfneaZZ743FT3KrbAq7lx6I28zPLWlFjYKYyr/6+QcVRX+6wle0GzFlVLxHdMr DScdpOYKQ3FoqDwaNZIz0Z+sJ9eveGkt2Rbb6duPuBEj6QlQT8YL1232bmSw3qjquEYy ffYE16Ez3VQ6alXQUudIpZgQs7yTiOA1F3zbNPnciH0IgWL8F+hHyz/5uaXtC5UBlrrH 7+ug== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1753737220; x=1754342020; 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=ezL2HT4b3NmDh/7FJ9thrkjKfd0k0fuvaqD/KBu7IHo=; b=SYDeBgdxU9VO6VMkBN/Js57lSjVypVy2FHg/LJtz/UxEVtiUZxVRbbCrQhU3Iuw9mE a8ljE/ocNEkDbaNEFTaervwDNtX1pcfH2igtdeUzMbCExYuuA7w+8I+FVvkL2nVBJdwY cGH6D9MLzfrBdW6YuDkNXfnce327BLvHCz7uO3SsiDe6ig1qvMTatUMWvzcqLvWmgFzl r3Lrtgo0TTn+v3nwctL64afsCqaY8v1/bklY2Q0lwzQiCoEY+YF2DJWbHCdjPb1xIxCT O+nr5qfKmA7Vh/s0mWhaTzdLn9GZ9x7NdJfUriEwKdQoUrWqhZzeYRc7bsIx6TfphWNQ uZrg== X-Gm-Message-State: AOJu0Yw/E3yiTvZO7DNPykh/JezYu0ClBQ8WgZQ/Wfo0LKvX4K4A3zBQ kX8gZ+pQ8SAgiZsmL32cSf+l2B2wI/tgW6hwmOsZuCVeWrZLDFzor85WsvAp45K+4ePgWjqGDff v9tEaAKgIJJqnGP5fHOOz7N2oaWivB/IS/4tXoIl8ZQ== X-Gm-Gg: ASbGnctTOqdSWSOV1/SM7Tv+4ygwI99nE3I7IJV2d1hNGCewQeiyfPg8WufUGyyvDyw sJbjuZ8ZeCmZGLluL88XkYJOWpoeLIdAmIxkMo3WBXXcaFMTPF+0sh5RsuxAa/yzbuhoV+gyhsz iD3ChHUPoRbMWzaNX/iMl8pTQotco8yeftzCwMFxWeULU8iz+J4QCBAKbnEiJNfZDvwgT733NG9 uR+5NYb X-Google-Smtp-Source: AGHT+IGU5zEaAQZbAerMXKnBXZtbhEa4jYgnNIOwNzF+95S1Rmi4aWXFyXyIgg+XxUHmWrWFvIlD5HJ2hrPCKSudV90= X-Received: by 2002:a05:6808:219f:b0:420:e4f3:e1fe with SMTP id 5614622812f47-42bb71f47a9mr8591095b6e.2.1753737220089; Mon, 28 Jul 2025 14:13:40 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Doruk Yilmaz Date: Tue, 29 Jul 2025 00:13:27 +0300 X-Gm-Features: Ac12FXyA_2RwLLD2AAzeRX4gEI5mks_dRRg43yyc3_-0qwhxPF4hzbIJXQTGpt4 Message-ID: Subject: Re: [Patch] add new parameter to pg_replication_origin_session_setup To: Amit Kapila , Euler Taveira Cc: pgsql-hackers@lists.postgresql.org 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, Mar 3, 2025 at 6:39=E2=80=AFAM Amit Kapila wrote: > > To use replication_origin by multiple processes, one must maintain the > commit order as we do internally by allowing the leader process to > wait for the parallel worker to finish the commit. See comments atop > replorigin_session_setup(). Now, we could expose the pid parameter as > proposed by the patch after documenting the additional requirements, > but I am afraid that users may directly start using the API without > following the commit order principle, which can lead to incorrect > replication. So, isn't it better to do something to avoid the misuse > of this feature before exposing it? Wouldn't mentioning/describing needing to follow the commit order principle on the documentation be enough for this? It is quite an advanced feature that I don't believe person intending to use it won't start with reading documentation first. Is there any updates on the commit? I see that intended commitfest window e= nded. Thanks, Doruk Y=C4=B1lmaz