|
Hi there,
Welcome to the pganalyze newsletter for August 2022!
Today, we open up registrations for our upcoming webinar "Optimizing Postgres I/O performance and costs", share improvements for configuring Amazon Aurora clusters with pganalyze, inform you about our updated Privacy Policy, and walk you through the outcomes of our recent communication preferences survey.
We'll also share our latest "5mins of Postgres" episodes, let you know how you can get your very own pganalyze sticker and coaster, and the most recent product updates to the pganalyze app. Lastly, if you like what we're building here at pganalyze we'd appreciate if you could review us on either G2 or TrustRadius. More below!
- - -
Upcoming Webinar on Sept. 22nd, 2022: Optimizing Postgres I/O performance and costs In this webinar we’ll take a deep dive into I/O optimization in Postgres, and how tuning I/O helps reduce overall database costs. We’ll review the different sources of read and write I/O in Postgres, including queries, indexes, internal cache usage and background processes. We’ll also take a look at relevant configuration settings and how to tune them.
Webinar Registration: Optimizing Postgres I/O performance and costs→
- - -
Easier integration of Amazon Aurora clusters with pganalyze
Are you using pganalyze to monitor an Amazon Aurora PostgreSQL cluster? You might have tried using the cluster endpoint in your collector configuration, but then ran into errors with Log Insights or Automated EXPLAIN, instead requiring the use of individual instance endpoints. We've heard your feedback, and we have now made it easier to automatically monitor the current writer or reader instance with pganalyze.
When you upgrade to the collector release 0.45.1 or newer, you can now specify cluster endpoints like this:
db_host: mydbcluster.cluster-123456789012.us-east-1.rds.amazonaws.com
The collector now automatically detects the current writer instance, or reader instance (in a two-node cluster when given the "cluster-ro" endpoint), saving you time and ensuring the configuration auto-updates when the cluster fails over. When upgrading make sure to grant the IAM policy for the collector the "rds:DescribeDBClusters" permission.
Have other ideas for how pganalyze could work better with Amazon Aurora? Let us know - we would be happy to hear your feedback!
- - -
Updated Privacy Policy, Data Processing Addendum and CCPA notice
We've updated our Privacy Policy effective August 31, 2022 to reflect new requirements regarding data transfers between the EU and the US, as well as clarifications in regards to the California Consumer Privacy Act (CCPA). We have also removed Perfect Audience as a data sub-processor.
Read the updated Privacy Policy →
- - -
Get your very own pganalyze sticker and coaster!
We've recently had a small batch of stickers and coasters printed, and still have a few left. Thanks to Enrique for snapping this picture and sharing it with us.
Want one too? Just reply back to this email with your mailing address and we'll put some in the mail! (supplies are limited)
- - -
5mins of Postgres - episodes from August: We talk about Postgres lock conflicts on Amazon Aurora and tuning max_standby_streaming_delay and hot_standby_feedback, why you should implement retry logic with Aurora and how you can avoid query conflicts on Postgres with Amazon Aurora's fast clones. We’ll also look at an effective setup from the Twitch team for these settings. (share this episode here)
E30: Postgres performance puzzle, Linux readahead and tuning effective_io_concurrency→ We show an interesting Postgres performance puzzle by Jeremy Schneider and talk about Linux readahead and how to tune effective_io_concurrency. (share this episode here)
E31: Postgres security patch release, spotting vulnerable extensions and securing the public schema→ We walk through the latest Postgres patch releases and a security bug that got fixed. We also talk about extension security in Postgres, pgspot, pghostile, as well as the public schema and a change in Postgres 15 to make it more secure. (share this episode here)
E32: Benchmarking and improving query network latency using tc, COPY and pipeline mode→ We talk about network latency, how it impacts your query performance and how to improve it by using pipeline mode or COPY in Postgres. We also take a look at traffic control with the Linux tc tool. (share this episode here)
Subscribe to the pganalyze YouTube channel to stay up to date about our weekly videos→
- - -
Results from our communications preferences survey: Manuel recently sent out a survey asking you about how you'd best like us to reach out to you. It's important to us to treat you well and communicate to you in a way that makes most sense to you. Below, Manuel is sharing the results based on the responses of over 200 participants.
We mainly were interested in the style of email you'd like to receive from us and how often you'd want to read our pganalyze newsletter. Here are the main take-aways and what we'll do going forward:
If you have any questions or comments regarding these decisions feel free to respond to this email - we are reading every response!
- - -
Review us on G2 and TrustRadius: We recently added pganalyze to the G2 and TrustRadius review portals. If you are using pganalyze and feel good about recommending it we'd appreciate if you'd review us on either of these portals: Thanks so much, we appreciate it!
- - -
Product changes in August:
- - -
As always, I'm happy to hear from you and am personally reading all of your responses. Looking forward to your thoughts and seeing you in our upcoming webinar on I/O performance!
Have a nice day! Lukas & the pganalyze team
PS: If you're interested in giving pganalyze a try you can learn more about it here. Of course, I'd be happy to walk you through a demo on a video call. You can book a 30 minute meeting with me here. Or, if you have general requests, feel free to get in touch with us here.
|
