Postgres

This year has gotten off to an utterly ridiculous start. Now that I’m working with pgEdge, they’re encouraging me to submit to every possible conference that will have me. So I have. In addition to that, there are a few company events which require travel, so I’m globe-trotting for those too. All in all, this is what my schedule looks like this year so far: Feb 3-7 - Spock developer symposium in Alexandria March 5-8 - Presenting What’s our Vector, Victor?

I’ve been somewhat tight-lipped about my job hunt, but not through any particular desire to obfuscate. No, I’ve just been laying low because I caught Covid right before Christmas and spent the last couple weeks recuperating. Just my luck, getting sick again so soon after whatever got me following Thanksgiving, and effectively missing the holidays as a consequence. Still, I had an informal offer before being incapacitated, so I only had to worry about recovering.

Postgres Conference Seattle 2024 partnered up with PASS this year to present a united database front. They accepted my “Kubernetes Killed the High Availability Star” talk, which I graciously gave on the last day of the conference. The next talk in that room wasn’t for another hour, so I had plenty of time to talk shop with attendees, about the future of Postgres, high availability, and Kubernetes in general.

If you weren’t there and missed out on the fun, this is your chance to catch up and enjoy a few of my notorious bad puns along the way. Let me tell you why the concept of Postgres HA is dead.

Postgres Conference Seattle 2024 partnered up with PASS this year to present a united database front. They accepted my “What’s our Vector, Victor?” talk, which I graciously gave on the first day of the conference. If you weren’t there and missed out on the fun, this is your chance to catch up and maybe get a bit more information that was cut for length. Let me tell you why RAG is the future, and how Postgres and pg_vectorize make it a reality.

Things always start in an unassuming way, don’t they? Having recently returned from a short paternity leave, the Tembo CTO wanted a short meeting last Friday morning, and I assumed it was so he could catch up with our projects. Instead, he informed me that the company was changing direction, and my services would no longer be necessary. I knew the company was beginning a sharp pivot, but was hoping my project would survive the tumult.