> 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.
Went right over my head LOL it actually made me angry reading it earlier hahaha
Well, that makes a lot of sense. I guess I didn't take it as a joke because I've seen some of these things recommended before (including not checking in lockfiles) in other contexts.
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
I don’t see pricing on the website but the iOS app shows “In App purchases”. Is there a reason why you wouldn’t mention pricing on the website you linked?
Sequence is reinventing accounts receivable for modern businesses. We're building a flexible toolkit that helps B2B finance teams scale their revenue collection infrastructure with a world-class billing engine.
Backed by top investors including a16z and Salesforce Ventures, we're a team with decades of experience building category-defining marketplace, fintech, and enterprise software.
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.
Big +1 for Bunny.net - I moved my current company to Bunny and it's been excellent. Super fast (for our PoPs at least), reasonable pricing, love the image optimizer & edge rules (especially for solving header issues when embedding documents), has a Terraform provider, and I was able to set most of it up in a day. Was a night and day difference from GCP's Cloud CDN
Good to see Skip on the home page! We were evaluating Skip just a couple weeks ago for a side project.
The issue we ran into is that we've already built a native iOS app with SwiftUI + a bit of UIKit. Integrating Skip with an existing app seemed like a significant task
Does that hold true in your experiences? Do you have any examples of small- or medium-sized existing apps that have migrated to Skip?
It’s missing things that are harder to work around if you already have code relying on those missing bits or done in an architecture it can’t transpile
The GitHub readme is well documented but hard to know how that translates into the dev exp, like with scaling or upgrades and if its features are comparable to managed Postgres providers (I'd assume no but happy to be proven wrong!)
I used to use it but what got me was letting my Dokku install get stale and then upgrading a whole bunch of versions in a row. The old plugin broke, the new one wasn’t compatible, there were version issues.
Nowadays I just run Postgres directly on my Debian box and just create a new user/DB for ever application, then set an env variable for the Dokku app to connect. Postgres is so solid to begin with that it requires no babysitting unless you have very intense workloads (at which point either use a hosted solution or start thinking about how you’ll do your own DBA).
> 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.