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 1nLINP-0006FC-0t for pgsql-hackers@arkaria.postgresql.org; Sat, 19 Feb 2022 05:33:47 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nLINN-0001bu-TQ for pgsql-hackers@arkaria.postgresql.org; Sat, 19 Feb 2022 05:33:45 +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 1nLINN-0001bl-K4 for pgsql-hackers@lists.postgresql.org; Sat, 19 Feb 2022 05:33:45 +0000 Received: from mail-yb1-xb2a.google.com ([2607:f8b0:4864:20::b2a]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nLINK-0005oy-Ni for pgsql-hackers@lists.postgresql.org; Sat, 19 Feb 2022 05:33:45 +0000 Received: by mail-yb1-xb2a.google.com with SMTP id bt13so23539658ybb.2 for ; Fri, 18 Feb 2022 21:33:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ccMNsMG3O2yvpr2OnYTSErbjKC+AyZc4dWHkSkcA3n8=; b=e/1TXz7qWTXJZnc6RPqQQIVZKAP7V9VTj2cGqM4I0FdLj9iZgvrBaJfpjnjWYi/Kdg mBCU9kJW27+Fxe/sF5fGL5b/WEbD8st0ZHx3ERo/CS3I/DeusgN/NyVsKaJmOrUh8jCX P00jfVX7OD+vjFN9Cb67IdDDpU2TfsvwgtRk/PV7gvl4SPMHn55Wi6Ho1d9I8Cx6qT6L vMeYZYmWV79s9Hq5ZiOQt0tvUbLNYzR0ygnL/aQxWr488RXCvk1/vh4PXAWPcm4o+GLM jmN5l51BFZA7VTNVh2+ZIvl+TkX6txbGZ5EXLsBSonBhbIkEcHdoaJRBUL6Cdga4kPcl cmxg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ccMNsMG3O2yvpr2OnYTSErbjKC+AyZc4dWHkSkcA3n8=; b=F3HD0P66GCLB9cjQew1VuiRJCGhLNcGoZuOT5F8JI1xW9K+rqhBYn7EjZdDXaOrUty lR7sRv2xwOoH30Z03JT4D2vRmbEaLlX475tSYhuY6Bmv11x8+P57FFX0l4FeQkHDtw9w n8Otod+T8usSxDoJCtMaznf0psfcFvW8r7TL7e8lyjJE+VdLX4r5JNxoDOpOnbzZUXiN 3SR3xEb0cWq3OJXLNQtQ/+ZtM6/1hSaFPf85zhCe2kyDwwhRt+FidKDUFE/Hd8dsTPXE o6DLqD3wCtsTutTbr7R97SFt46Zck5BUuuC9IdabWY9uzZTmUxpWhFLwADatR1FGfdNf 83UA== X-Gm-Message-State: AOAM531myOBK+/o+yZ2ywbDYPAUgMe3TqSsPZYnDc5Vn8SIXnDgEZhba uFAdn3Ppa691aYKpS6O+VT71zHHLB8uC2pDK3uJHbfTHvQ+WlQ== X-Google-Smtp-Source: ABdhPJwOK1XQ/YzI8MxX5PSo0eosxlX6zUAAHLfp6Y3iJz/uSdkbK5IkyeegRxRU61+kJyqdUvae+5F3jr0Tk+ZVas4= X-Received: by 2002:a5b:1d2:0:b0:624:4198:2ea7 with SMTP id f18-20020a5b01d2000000b0062441982ea7mr7289866ybp.349.1645248820809; Fri, 18 Feb 2022 21:33:40 -0800 (PST) MIME-Version: 1.0 References: <90b4e402-3f07-14f4-deca-5eaca31f70a3@enterprisedb.com> <22aef14d-0ea1-9044-c2e7-29f88762eaec@enterprisedb.com> <32540e16-fab6-f790-b99b-5a8fca8bde52@enterprisedb.com> <3B014BE4-EE61-4834-8FF6-937B43C46BC7@enterprisedb.com> <3d68b45a-ceb5-6824-3a39-f53411fd0c88@enterprisedb.com> <802f8b1b-a798-be52-c829-7f0fb9faafd5@enterprisedb.com> <983bf0c7-9757-fd13-3896-8452cf4c4c52@enterprisedb.com> <9211312a-6501-1caf-ee7b-c0d4814b6091@enterprisedb.com> <41ada110-bc7c-32a3-08bd-fb5023dd74ba@enterprisedb.com> <2eed0f76-3a1a-8b8b-ac1b-e0f9a0d98287@enterprisedb.com> In-Reply-To: From: Amit Kapila Date: Sat, 19 Feb 2022 11:03:29 +0530 Message-ID: Subject: Re: logical decoding and replication of sequences To: Tomas Vondra Cc: Peter Eisentraut , Petr Jelinek , 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 Sat, Feb 19, 2022 at 7:48 AM Tomas Vondra wrote: > > Do we need to handle both FOR ALL TABLES and FOR ALL SEQUENCES at the > same time? That seems like a reasonable thing people might want. > +1. That seems reasonable to me as well. I think the same will apply to FOR ALL TABLES IN SCHEMA and FOR ALL SEQUENCES IN SCHEMA. -- With Regards, Amit Kapila.