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 1lAI2t-00080n-Pn for pgsql-admin@arkaria.postgresql.org; Thu, 11 Feb 2021 19:54:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lAI2s-0004e6-OL for pgsql-admin@arkaria.postgresql.org; Thu, 11 Feb 2021 19:54:34 +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 1lAHtN-0001eI-6A for pgsql-admin@lists.postgresql.org; Thu, 11 Feb 2021 19:44:45 +0000 Received: from forward3-smtp.messagingengine.com ([66.111.4.237]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lAHtI-00058J-LD for pgsql-admin@postgresql.org; Thu, 11 Feb 2021 19:44:44 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailforward.nyi.internal (Postfix) with ESMTP id 65FF81940D2D; Thu, 11 Feb 2021 14:44:38 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 11 Feb 2021 14:44:38 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=wlhUD/+W2k0H9dc/lTE5dZuDOy5bcnxbLO0fhDiMx PA=; b=hLV/Q0dsqiDGBe/aCwPc0u2BKrdBPDWsZbeSfJkBh/lT4S42+ZXujhA0J 9RP+BKVKkrywXTYmrHBHGhhd+oTl7za/jhueUU5GDvZbr5C/5rCWNc1Os13eOfIn V4R/eoc6YageG0FPNikk2RxvT9TyQ5dbBVpYKDNobIr7P+VhamAqj4e0VAiY2eKQ OvjE3rPcJgv+0S0NqGLDRg/Hx38G/LAYGg4yQ2w5caSt2lbE/yfcYM/ToAm0ccAD 91Pu5o0tThb7xk1KrvhabBSNvbjjLSg9WurOe+6oHj/7mOeqeZPEek9xuCUzmtvp 7VmdPiTu2aFnVVQKZQ7nG37XMTnUQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrheelgdduvdekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepuffvfhfhohfkffgfgggjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvght vghrucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvghnth gvrhhprhhishgvuggsrdgtohhmqeenucggtffrrghtthgvrhhnpeehheeijefgvefhvdeh leekueevhfehhedvheetgffhteefgeeggfevjeejfffgvdenucfkphepkeejrddujeejrd eiledrudegtdenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhr ohhmpehpvghtvghrrdgvihhsvghnthhrrghuthesvghnthgvrhhprhhishgvuggsrdgtoh hm X-ME-Proxy: Received: from april.pezone.net (p57b1458c.dip0.t-ipconnect.de [87.177.69.140]) by mail.messagingengine.com (Postfix) with ESMTPA id E98FC240062; Thu, 11 Feb 2021 14:44:36 -0500 (EST) Subject: Re: pglogical with bytea values To: Dirk Krautschick , "pgsql-admin@postgresql.org" References: From: Peter Eisentraut Organization: EnterpriseDB Message-ID: <4701b79f-1328-c06e-1ad3-1d8eb38cb895@enterprisedb.com> Date: Thu, 11 Feb 2021 20:44:35 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2021-01-28 15:37, Dirk Krautschick wrote: > are there any known problems or limitations with bytea values and > logical replication with pglogical? bytea works just like any other data type, so no problem with pglogical. > I guess large objects are still an issue, right? right