From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Dirk Krautschick <Dirk.Krautschick@trivadis.com>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: pglogical with bytea values
Date: Thu, 11 Feb 2021 20:44:35 +0100
Message-ID: <4701b79f-1328-c06e-1ad3-1d8eb38cb895@enterprisedb.com> (raw)
In-Reply-To: <AM0PR05MB6082F9D2D66CB1E5463312DBE9BA9@AM0PR05MB6082.eurprd05.prod.outlook.com>
References: <AM0PR05MB6082F9D2D66CB1E5463312DBE9BA9@AM0PR05MB6082.eurprd05.prod.outlook.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: peter.eisentraut@enterprisedb.com, Dirk.Krautschick@trivadis.com
Subject: Re: pglogical with bytea values
In-Reply-To: <4701b79f-1328-c06e-1ad3-1d8eb38cb895@enterprisedb.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox