PeerDB (YC S23)

🚢 🚢 🚢

🛳 🎉 Shipping continues at full throttle. Here is our latest release, version 0.15.1: https://lnkd.in/gCf9rf5e. This release focuses on Security, Stability, and Usability. Goal was take PeerDB multiple steps further in providing an enterprise-grade CDC experience for Postgres A few highlights include: 🔐 Encrypting credentials stored in the peers table. 🚫 Option to disable metadata columns, enabling online migrations. 🚀 Faster Avro conversion. 📊 Better data-type handling. ⚡ Configurable settings page to tune and manage MIRRORs.

📣 🎉Big news coming your way! PeerDB Cloud is now SOC 2 Type 2 compliant. This is a major step forward in ensuring the world's best security and privacy for our customers. 🔒 We are committed to maintaining the highest standards in protecting your data. 🌐 Thank you for your continued trust and support! 🙏 Check out the full story here: https://lnkd.in/eQdm_NfQ

📣 🎉  At PeerDB, we're committed to delivering the fastest and most reliable Postgres replication experience. We rely on Postgres logical decoding for CDC. This blog captures all the intricacies we deal with in Postgres logical decoding in our day-to-day. We want to publish this blog as a reference for any Postgres user in the community using Postgres logical decoding! Below are the main takeaways: https://lnkd.in/gTQqsqKF 🔍 Monitor Replication Slot Growth: Unexpected growth can fill up storage and crash servers. Use tools like our PG Slot Notify bot to keep an eye on it. ⚡ Consume the Replication Slot Efficiently: Ensure continuous consumption to avoid inefficiencies and slowdowns. ⏳ Handle Long-Running Transactions: Configure statement_timeout and idle_in_transaction_session_timeout to prevent WAL buildup. 🔄 Use Logical Replication Protocols: Opt for proto_version v2 to handle in-flight transactions and improve performance. 💡 Avoid Inactivity Issues: Implement heartbeats or use pg_logical_emit_message to ensure consistent slot consumption. 🔧 Optimize Configurations: Adjust max_slot_wal_keep_size and logical_decoding_work_mem to manage disk space and memory usage. 🔄 Support DDL Changes: Leverage Relation and Type messages for schema changes. 📜 Handle TOAST Columns: Enable REPLICA IDENTITY FULL to capture large columns. ⚙️ Manage Generated Columns: Use in-flight transformations or ELT processes. 🔄 Prepare for Upgrades and Failovers: PostgreSQL 17 will support persistent replication slots through upgrades and failovers, simplifying maintenance. Have you faced challenges with Postgres Logical Decoding? How did you overcome them? Let's discuss! 💬🔗 #Postgres #DataReplication #LogicalDecoding #PeerDB #TechInsights

📣 🎉Big news coming your way! PeerDB Cloud is now SOC 2 Type 2 compliant. This is a major step forward in ensuring the world's best security and privacy for our customers. 🔒 We are committed to maintaining the highest standards in protecting your data. 🌐 Thank you for your continued trust and support! 🙏 Check out the full story here: https://lnkd.in/eQdm_NfQ

👀 Blog post on "Overcoming Pitfalls of Logical Decoding" was on hn front page over the weekend. If you haven't yet read the blog, you should go for it. Here goes the link: https://lnkd.in/gTQqsqKF

📣 🎉  At PeerDB, we're committed to delivering the fastest and most reliable Postgres replication experience. We rely on Postgres logical decoding for CDC. This blog captures all the intricacies we deal with in Postgres logical decoding in our day-to-day. We want to publish this blog as a reference for any Postgres user in the community using Postgres logical decoding! Below are the main takeaways: https://lnkd.in/gTQqsqKF 🔍 Monitor Replication Slot Growth: Unexpected growth can fill up storage and crash servers. Use tools like our PG Slot Notify bot to keep an eye on it. ⚡ Consume the Replication Slot Efficiently: Ensure continuous consumption to avoid inefficiencies and slowdowns. ⏳ Handle Long-Running Transactions: Configure statement_timeout and idle_in_transaction_session_timeout to prevent WAL buildup. 🔄 Use Logical Replication Protocols: Opt for proto_version v2 to handle in-flight transactions and improve performance. 💡 Avoid Inactivity Issues: Implement heartbeats or use pg_logical_emit_message to ensure consistent slot consumption. 🔧 Optimize Configurations: Adjust max_slot_wal_keep_size and logical_decoding_work_mem to manage disk space and memory usage. 🔄 Support DDL Changes: Leverage Relation and Type messages for schema changes. 📜 Handle TOAST Columns: Enable REPLICA IDENTITY FULL to capture large columns. ⚙️ Manage Generated Columns: Use in-flight transformations or ELT processes. 🔄 Prepare for Upgrades and Failovers: PostgreSQL 17 will support persistent replication slots through upgrades and failovers, simplifying maintenance. Have you faced challenges with Postgres Logical Decoding? How did you overcome them? Let's discuss! 💬🔗 #Postgres #DataReplication #LogicalDecoding #PeerDB #TechInsights

📣 🎉 Another week, another customer testimonial! This one is from Yuno, who is using PeerDB for their Postgres replication needs. They are using PeerDB Enterprise, which provides a production-grade experience of PeerDB through enterprise-ready K8S Helm charts. Thank you Federico Cipriani, Federico Falour, @Leonardo Janosch, Guido Farré and team for giving us the opportunity. Very grateful to be providing value! 🙏