> If the vulnerability were critical, someone would have merged it by now.
> GitHub Copilot can automatically suggest fixes for security vulnerabilities. Instead of updating to a patched version, let AI generate a workaround in your own code.
Agree with other commenters that the title is a bit confusing and should be renamed to something like "Is your Postgres workload read heavy or write heavy?"
But title aside, I found this post very useful for better understanding PG reads and writes (under the hood) and how to actually measure your workload
Curious if the tuning actions any different if you're using a non-vanilla storage engine like AWS Aurora or GCP AlloyDB or Neon?
Sequence | London / NYC (Hybrid) or EMEA (Remote) | Full-time | sequencehq.com
Sequence is reinventing accounts receivable for modern businesses.
We're one of the first a16z backed companies in Europe, building an AI first revenue automation platform that enables sales and finance teams to streamline the quoting, billing, invoicing and revenue workflow.
Our tech stack includes Kotlin, TypeScript, React, Postgres, and GCP. We're looking for engineers who enjoy being hands-on, shipping code, and working closely with customers to solve complex financial problems.
Open roles:
* Senior Product Engineer (Backend) | London / NYC (Hybrid) or EMEA (Remote) | £75k-110k + equity
> If the vulnerability were critical, someone would have merged it by now.
> GitHub Copilot can automatically suggest fixes for security vulnerabilities. Instead of updating to a patched version, let AI generate a workaround in your own code.