Thread: Pglogical 2.3.0 in AWS RDS 12.2
Hello everybody,
Has anybody succeeded with using pglogical in AWS Postgresql 12.2? They have pglogical v2.3.0, and it has this issue https://github.com/2ndQuadrant/pglogical/issues/240, which was fixed in the 2.3.1.
However, one cannot upgrade pglogical to 2.3.1 in RDS. Just curious if somebody found a work around. Otherwise, it seems unusable with RDS v12.2 right now.
The specific issue is:
The replication just does not start after creating a subscription. If I try synchronize, I see:
select pglogical.alter_subscription_synchronize('subscription1');
ERROR: could not get table list: ERROR: syntax error at or near "."
LINE 1: ...i.att_list, i.has_row_filter, i.nspname as i.nsptarget…
ERROR: could not get table list: ERROR: syntax error at or near "."
LINE 1: ...i.att_list, i.has_row_filter, i.nspname as i.nsptarget…
In the db log:
2020-06-01 05:05:59 UTC;user=replication;db=demandbase_production;app=subscription1_sync;client=3.217.57.139(10005);[52691-3] ERROR: syntax error at or near "." at character 89
2020-06-01 05:05:59 UTC;user=replication;db=demandbase_production;app=subscription1_sync;client=3.217.57.139(10005);[52691-4] STATEMENT: SELECT i.relid, i.nspname, i.relname, i.att_list, i.has_row_filter, i.nspname as i.nsptarget, i.relname as i.reltarget FROM (SELECT DISTINCT relid FROM pglogical.tables WHERE set_name = ANY(ARRAY['default','default_insert_only','ddl_sql'])) t, LATERAL pglogical.show_repset_table_info(t.relid, ARRAY['default','default_insert_only','ddl_sql']) i
In GIT:
user@MacBook-Pro pglogical (HEAD detached at REL2_3_1) $ git checkout REL2_3_0
Previous HEAD position was 19d6f4f Merge branch 'pglogical2-fix-revert' into REL2_x_STABLE
HEAD is now at 4d53ca4 pglogical_create_subscriber: Fix for PostgreSQL 12
user@MacBook-Pro pglogical (HEAD detached at REL2_3_0) $ grep -R "i.nspname as i.nsptarge" *
pglogical_rpc.c: " i.has_row_filter, i.nspname as i.nsptarget, i.relname as i.reltarget"
ipolishchuk@MacBook-Pro pglogical (HEAD detached at REL2_3_0) $
Source Postgresql 9.6 pglogical 2.3.1 or 2.3.2
Target AWS RDS Postgresql 12.2 pglogical 2.3.0
Thank you
Igor Polishchuk
On 6/1/20 09:39, Igor Polishchuk wrote: > Hello everybody, > Has anybody succeeded with using pglogical in AWS Postgresql 12.2? > They have pglogical v2.3.0, and it has this > issue https://github.com/2ndQuadrant/pglogical/issues/240, which was > fixed in the 2.3.1. > However, one cannot upgrade pglogical to 2.3.1 in RDS. Just curious if > somebody found a work around. Otherwise, it seems unusable with RDS > v12.2 right now. When I can, I usually encourage people to report RDS specific issues on the AWS forums; the postgresql.org mailing lists are most suited for questions that are not RDS-specific but apply to PostgreSQL in general. https://forums.aws.amazon.com/forum.jspa?forumID=60 That said - AWS is aware of this issue. Extension updates on RDS are coupled with minor releases (typically coming every three months from postgresql.org), so just keep checking the future new minor releases on RDS until you see something. And if you don't have a support agreement with AWS then make noise on the forums, product managers do read them. :) The pgLogical extension is published and maintained by 2ndQuadrant. It seems to me that a good place to discuss whether any temporary workaround exists might be right on the github issue itself even though it's closed. (Does 2ndQuadrant have any email lists or forums?) I haven't looked at this issue so I don't know if there's any workaround that could be used with 2.3.0 on RDS. I also don't know much about 2ndQuadrant's support agreements/offerings, and whether there's something there that could give general advice about the open source pgLogical extension. Hope this helps, Jeremy -- Jeremy Schneider Database Engineer Amazon Web Services
On 6/1/20 15:33, Jeremy Schneider wrote: > I also don't know much about > 2ndQuadrant's support agreements/offerings, and whether there's > something there that could give general advice about the open source > pgLogical extension. Just noticed that Peter replied on the other thread... listen to whatever he says. :) -J -- Jeremy Schneider Database Engineer Amazon Web Services
On 6/1/20 3:33 PM, Jeremy Schneider wrote: > On 6/1/20 09:39, Igor Polishchuk wrote: >> Hello everybody, >> Has anybody succeeded with using pglogical in AWS Postgresql 12.2? >> They have pglogical v2.3.0, and it has this >> issue https://github.com/2ndQuadrant/pglogical/issues/240, which was >> fixed in the 2.3.1. >> However, one cannot upgrade pglogical to 2.3.1 in RDS. Just curious if >> somebody found a work around. Otherwise, it seems unusable with RDS >> v12.2 right now. > > When I can, I usually encourage people to report RDS specific issues on > the AWS forums; the postgresql.org mailing lists are most suited for > questions that are not RDS-specific but apply to PostgreSQL in general. > > https://forums.aws.amazon.com/forum.jspa?forumID=60 > > That said - AWS is aware of this issue. Extension updates on RDS are > coupled with minor releases (typically coming every three months from > postgresql.org), so just keep checking the future new minor releases on > RDS until you see something. And if you don't have a support agreement > with AWS then make noise on the forums, product managers do read them. :) Seems supporting bug releases is not something that should require making noise. The user is locked out of applying the fix themselves and your response is to keep them stuck on a version with known issues. We have different ideas of customer service. > > The pgLogical extension is published and maintained by 2ndQuadrant. It > seems to me that a good place to discuss whether any temporary > workaround exists might be right on the github issue itself even though > it's closed. (Does 2ndQuadrant have any email lists or forums?) I > haven't looked at this issue so I don't know if there's any workaround > that could be used with 2.3.0 on RDS. I also don't know much about > 2ndQuadrant's support agreements/offerings, and whether there's > something there that could give general advice about the open source > pgLogical extension. > > Hope this helps, > Jeremy > -- Adrian Klaver adrian.klaver@aklaver.com