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 1o8LsI-000629-Fw for pgsql-hackers@arkaria.postgresql.org; Mon, 04 Jul 2022 13:12:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1o8LsH-00010F-9i for pgsql-hackers@arkaria.postgresql.org; Mon, 04 Jul 2022 13:12:25 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o8LsG-0000zu-L1 for pgsql-hackers@lists.postgresql.org; Mon, 04 Jul 2022 13:12:25 +0000 Received: from smtp-fw-80006.amazon.com ([99.78.197.217]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o8LsA-0006di-Up for pgsql-hackers@postgresql.org; Mon, 04 Jul 2022 13:12:24 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amazon.com; i=@amazon.com; q=dns/txt; s=amazon201209; t=1656940339; x=1688476339; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to; bh=bXW3Ji8L/2YbLfD1nARI51asyAN4iS2sDe4JF6UvYsU=; b=a6AzaK4YypDhl7F7Xrm2VynueIc7WOM1PO2peRouLZqvPzZ8FKx+50UY lAP0HwH0GvxJcLH/7RoVDWEP0RA9s0rJ/SF+pAuM/p2PWNJhRQta+qp/a KSrwRis/YiBcw2R4QzSVvdzrXK4k5EnPja61MdQsSVsbKJo0KgyBOhBJw 4=; X-IronPort-AV: E=Sophos;i="5.92,243,1650931200"; d="scan'208,217";a="104581404" Received: from pdx4-co-svc-p1-lb2-vlan2.amazon.com (HELO email-inbound-relay-iad-1e-90d70b14.us-east-1.amazon.com) ([10.25.36.210]) by smtp-border-fw-80006.pdx80.corp.amazon.com with ESMTP; 04 Jul 2022 13:12:15 +0000 Received: from EX13D03EUC003.ant.amazon.com (iad12-ws-svc-p26-lb9-vlan3.iad.amazon.com [10.40.163.38]) by email-inbound-relay-iad-1e-90d70b14.us-east-1.amazon.com (Postfix) with ESMTPS id 5E202C0331; Mon, 4 Jul 2022 13:12:13 +0000 (UTC) Received: from [192.168.13.176] (10.43.161.228) by EX13D03EUC003.ant.amazon.com (10.43.164.192) with Microsoft SMTP Server (TLS) id 15.0.1497.36; Mon, 4 Jul 2022 13:12:09 +0000 Content-Type: multipart/alternative; boundary="------------F1eyfHKfhDv6yh7AMwYBiaoL" Message-ID: <0ccc31f3-4e6b-19ed-7944-800c30610f23@amazon.com> Date: Mon, 4 Jul 2022 15:12:05 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.11.0 Subject: Re: Minimal logical decoding on standbys Content-Language: en-US To: Ibrar Ahmed CC: Andres Freund , Robert Haas , Alvaro Herrera , Amit Khandekar , , tushar , Rahila Syed , pgsql-hackers References: <202107281526.o74ieuj6sj7z@alvherre.pgsql> <2b14d595-1e8b-e5b6-6098-6a11d19fa1c7@amazon.com> <688cbedf-a172-f0d8-8352-d4ea223bceeb@amazon.com> <20211028210755.afmwcvpo6ajwdx6n@alap3.anarazel.de> <0d8fe359-e6aa-4997-7e61-19d3dba360e0@amazon.com> From: "Drouvot, Bertrand" In-Reply-To: X-Originating-IP: [10.43.161.228] X-ClientProxiedBy: EX13D30UWB003.ant.amazon.com (10.43.161.83) To EX13D03EUC003.ant.amazon.com (10.43.164.192) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --------------F1eyfHKfhDv6yh7AMwYBiaoL Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit Hi, On 7/1/22 10:03 PM, Ibrar Ahmed wrote: > > On Thu, Jun 30, 2022 at 1:49 PM Drouvot, Bertrand > wrote: > > I'm going to re-create a CF entry for it, as: > > - It seems there is a clear interest for the feature (given the time > already spend on it and the number of people that worked on) > > - I've in mind to resume working on it > > I have already done some research on that, I can definitely look at it. > Thanks! This feature proposal is currently made of 5 sub-patches: 0001: Add info in WAL records in preparation for logical slot conflict handling 0002: Handle logical slot conflicts on standby 0003: Allow logical decoding on standby. 0004: New TAP test for logical decoding on standby 0005: Doc changes describing details about logical decoding I suggest that we focus on one sub-patch at a time. I'll start with 0001 and come back with a rebase addressing Andres and Robert's previous comments. Sounds good to you? Thanks -- Bertrand Drouvot Amazon Web Services:https://aws.amazon.com --------------F1eyfHKfhDv6yh7AMwYBiaoL Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: 8bit

Hi,

On 7/1/22 10:03 PM, Ibrar Ahmed wrote:

On Thu, Jun 30, 2022 at 1:49 PM Drouvot, Bertrand <bdrouvot@amazon.com> wrote:
I'm going to re-create a CF entry for it, as:

- It seems there is a clear interest for the feature (given the time
already spend on it and the number of people that worked on)

- I've in mind to resume working on it

I have already done some research on that, I can definitely look at it.

Thanks!

This feature proposal is currently made of 5 sub-patches:

0001: Add info in WAL records in preparation for logical slot conflict handling
0002: Handle logical slot conflicts on standby
0003: Allow logical decoding on standby.
0004: New TAP test for logical decoding on standby
0005: Doc changes describing details about logical decoding

I suggest that we focus on one sub-patch at a time.

I'll start with 0001 and come back with a rebase addressing Andres and Robert's previous comments.

Sounds good to you?

Thanks

-- 
Bertrand Drouvot
Amazon Web Services: https://aws.amazon.com
--------------F1eyfHKfhDv6yh7AMwYBiaoL--