From: | Andreas Joseph Krogh <andreas(at)visena(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pglogical vs. built-in logical replication in pg-10 |
Date: | 2017-06-22 10:38:12 |
Message-ID: | VisenaEmail.10.a4b6b80839ea34f0.15ccf5d6e2f@tc7-visena |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
På torsdag 22. juni 2017 kl. 11:43:02, skrev Achilleas Mantzios <
achill(at)matrix(dot)gatewaynet(dot)com <mailto:achill(at)matrix(dot)gatewaynet(dot)com>>:
On 22/06/2017 11:21, Andreas Joseph Krogh wrote:
Hi.
1. Why should one prefer built-in logical replication in pg-10 to pglogical,
does it do anything pglogical doesn't?
It seems pglogical is more feature-rich...
2. As I understand built-in logical replication in pg-10 doesn't support
large-objects, which we use a lot. Does pglogical replicate large objects? I
cannot find any notes about large-objects under "Limitations and Restrictions":
https://www.2ndquadrant.com/en/resources/pglogical/pglogical-docs/
<https://www.2ndquadrant.com/en/resources/pglogical/pglogical-docs/>
You may do a simple test, create a table with a largeobject and try to read
the logical stream, if it cannot represent the lo_import, lo_open, lowrite,
lo_close (and I 'd bet they can't be encoded) then neither pglogical (being
based on the same logical decoding technology) will support them
The point of email-lists like this is that one may share knowledge so one
doesn't have to test everything one self, and can build on knowledge from
others. I'm looking for an answer from someone who's not betting, but knows.
Thanks.
-- Andreas Joseph Krogh
CTO / Partner - Visena AS
Mobile: +47 909 56 963
andreas(at)visena(dot)com <mailto:andreas(at)visena(dot)com>
www.visena.com <https://www.visena.com>
<https://www.visena.com>
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2017-06-22 12:57:43 | Re: enable PostgreSQL SSL from RPM package installation |
Previous Message | Moreno Andreo | 2017-06-22 09:43:39 | Re: "joining" table records |