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 1nMzmz-0005gb-3Z for pgsql-hackers@arkaria.postgresql.org; Wed, 23 Feb 2022 22:07:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nMzmS-0005gN-By for pgsql-hackers@arkaria.postgresql.org; Wed, 23 Feb 2022 22:06:40 +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 1nMzmR-0005gB-Ds for pgsql-hackers@lists.postgresql.org; Wed, 23 Feb 2022 22:06:40 +0000 Received: from wout4-smtp.messagingengine.com ([64.147.123.20]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nMzmO-00018U-MY for pgsql-hackers@lists.postgresql.org; Wed, 23 Feb 2022 22:06:38 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 0D1603201FB9; Wed, 23 Feb 2022 17:06:34 -0500 (EST) Received: from imap49 ([10.202.2.99]) by compute4.internal (MEProxy); Wed, 23 Feb 2022 17:06:35 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eulerto.com; h= cc:cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm1; bh=RGd+WEE/ot65xmbBejybNyBjt8LI0cOc6vijsO PsnFw=; b=OJ0NYzUYLgFo9Bp+5zduGuWITY5e0SZYqiQuEZGlBAw/rT5NtR9EYk Wj3QMYg9+OQJUL4dq2yZcm4HQbcDk+sF0dMy9PBpwkH6EWmm5iSFMUzAcGlXqJxa 0sUFO6sT/0Usd2TRU1FQYsCYI/RUB4PFxls8AwqqParqCOftn9NRro/XwWamB8lO aI1Cu19xDP6doJUAE1m6tUFMd+K1JJimx0Tg2ZZPZxPUZX4ZxqFQMyhBNaKO8rnM qnjt7e64CDtPODvzxJCi4GGVw9pEzzCDl//N+lb5qzEZehV/RpG6MdzQ8j7qo0SF VSgswDRCp20gfCsgcsv2Yus7gv/0WHgg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=RGd+WEE/ot65xmbBe jybNyBjt8LI0cOc6vijsOPsnFw=; b=cDzYybymlIHvN6QCiA6SQW7ySpuV7LwPM kCEIWttuRDZOH5/gecLqc804Upm2etTvbIsKpkjozzClQhOjxII8On0foSCL2sCI ug1xVlx7hlqISkJO/QorRRJPLOR0hjcW1aSc18ZnO9nmmZ4kpCjYALb3EwJ4Wkq0 C0M3lYXFJQfz8unEpaz11o0Ng8DEEpPSEzWIBWJUH5Emq36kTw8AeoWZy5Hnd4m4 DwLyg+hVng5EnfxL7y5LBDJdsO8q+YSAO9eK0K3pueA13HYYn49gpPeY8WZa+0PD UupOVKhPOQLYzxRIdOZuys00tlGUPddB+TyPAHTSM3e929G0HWNNQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrledtgdduheegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesrgdtreerreertdenucfhrhhomhepfdfguhhl vghrucfvrghvvghirhgrfdcuoegvuhhlvghrsegvuhhlvghrthhordgtohhmqeenucggtf frrghtthgvrhhnpeduhfejgfevveeuffehudevhfdtgfdtudelieffvdetieehheejuedu teektdffvdenucffohhmrghinhepphhusghlihgtrghtihhonhdrhhhofidpvghnthgvrh hprhhishgvuggsrdgtohhmnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehm rghilhhfrhhomhepvghulhgvrhesvghulhgvrhhtohdrtghomh X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 32B57F6007E; Wed, 23 Feb 2022 17:06:34 -0500 (EST) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.5.0-alpha0-4778-g14fba9972e-fm-20220217.001-g14fba997 Mime-Version: 1.0 Message-Id: In-Reply-To: References: <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> <9defb937-20a9-1d9f-6972-f1c4b4da4f73@enterprisedb.com> <0476eb3a-bfe7-9477-540c-ac42d1f16760@enterprisedb.com> <4e158021-248d-43ad-95e5-943334bd1007@www.fastmail.com> Date: Wed, 23 Feb 2022 19:05:58 -0300 From: "Euler Taveira" To: "Tomas Vondra" , "Amit Kapila" Cc: "Peter Eisentraut" , "Petr Jelinek" , "PostgreSQL Hackers" Subject: Re: logical decoding and replication of sequences Content-Type: multipart/alternative; boundary=7664f3233d634af18182fad86efe6890 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --7664f3233d634af18182fad86efe6890 Content-Type: text/plain On Wed, Feb 23, 2022, at 4:18 PM, Tomas Vondra wrote: > On 2/23/22 18:33, Euler Taveira wrote: > > On Wed, Feb 23, 2022, at 1:07 PM, Tomas Vondra wrote: > >> Maybe, but I don't think it's very common to have that many > >> schemas added to the same publication. And it probably does not > >> make much difference whether you have 1000 or 2000 items in the > >> list - either both are acceptable or unacceptable, I think. > > > > Wouldn't it confuse users? Hey, duplicate publication. How? Wait. > > Doh. > > > > I don't follow. Duplicate publications? This talks about rows in > pg_publication_namespace, not pg_publication. I was referring to Publications: "testpub_schemas" (sequences) "testpub_schemas" (tables) versus Publications: "testpub_schemas" (tables, sequences) I prefer the latter. -- Euler Taveira EDB https://www.enterprisedb.com/ --7664f3233d634af18182fad86efe6890 Content-Type: text/html Content-Transfer-Encoding: quoted-printable
On Wed, Feb 23,= 2022, at 4:18 PM, Tomas Vondra wrote:
On 2/23/22 18:33, Euler Taveira wrote:
> On Wed, Feb 23, 2022, at 1:07 PM, Tomas Vondra wrote:
<= /div>
>> Maybe, but I don't think it's very common to have tha= t many
>> schemas added to the same publication. And= it probably does not
>> make much difference whethe= r you have 1000 or 2000 items in the
>> list - eithe= r both are acceptable or unacceptable, I think.
>
> Wouldn't it confuse users? Hey, duplicate publication. How= ? Wait.
> Doh.

<= br>
I don't follow. Duplicate publications? This talks about r= ows in
pg_publication_namespace, not pg_publication.
I was referring to

&n= bsp; Publications:
      "testpub= _schemas" (sequences)
      "test= pub_schemas" (tables)

versus

=
  Publications:
    &n= bsp; "testpub_schemas" (tables, sequences)

= I prefer the latter.


--
E= uler Taveira

--7664f3233d634af18182fad86efe6890--