Re:PostgreSQL 15: Stats Collector Gone? What’s New?
by paulryanrogers on Sunday August 28, 2022 @08:50PM
(#32633718)
Major version jumps are always fun. Recently I discovered RDS recommends pglogical over built in replication for a reason, the latter doesn't work well in RDS with larger than RAM replica logs.
[ Parent
| on HN ]
Re:PostgreSQL 15: Stats Collector Gone? What’s New?
by olau on Monday August 29, 2022 @04:05AM
(#32635777)
Aurora doesn't work with a query that computes a temporary table larger than memory either. Amazon's Postgres things are not Postgres.
Re:PostgreSQL 15: Stats Collector Gone? What’s New?
by paulryanrogers on Monday August 29, 2022 @09:33AM
(#32638012)
I wasn't using Aurora at the time. And I don't expect non-Aurora RDS to be exactly the same as vanilla Postgres either. Still, it was surprising that the old Pg solution is supported (pglogical) while the new one wasn't yet, at least for my version jump.
Re:PostgreSQL 15: Stats Collector Gone? What’s New?
by PikachuEXE on Monday August 29, 2022 @01:19AM
(#32635018)
I have never used RDS.
Anyway here is a post for using built-in logical replication.
https://dev.to/pikachuexe/postgresql-logical-replication-for...
Re:PostgreSQL 15: Stats Collector Gone? What’s New?
by paulryanrogers on Monday August 29, 2022 @09:31AM
(#32637988)
Posts like this didn't help in my case. Though depending on versions being replicated and RDS settings it could work.
Re:PostgreSQL 15: Stats Collector Gone? What’s New?
by PikachuEXE on Monday August 29, 2022 @09:57PM
(#32645823)
Ya there are many managed services and limitations around those.
Only throwing out this as a reference.
Re:PostgreSQL 15: Stats Collector Gone? What’s New?
by taspeotis on Sunday August 28, 2022 @09:42PM
(#32633956)
Hey, we use logical replication on RDS. Never considered pglogical. Do you have a link to Amazon’s recommendation of pglogical?
Re:PostgreSQL 15: Stats Collector Gone? What’s New?
by paulryanrogers on Sunday August 28, 2022 @10:01PM
(#32634062)
So I was using their guide for minimal downtime upgrades [0], see option 'D'. And I was replicating Pg 11 to 14. Logical replication appeared to work in that case yet big tables would never catch up or appear to get truncated. If you're replicating among nodes at the same Pg version then built-in replication may work for you.
Once I switched to pglogical jumping major versions worked as intended. Now it's possible in the rush I used the wrong setting somewhere and built-in logical replication can work between major versions. Though I lost enough time experimenting I'll keep using pglogical until AWS officially recommends something else.
[0] https://aws.amazon.com/blogs/database/part-1-upgrade-your-am...