News

I may finally have some respite from my hectic schedule full of flying all over the continental United States. On the other hand, I’m typing this very post from the airport, so perhaps not? The yearly EdgeFest company event was the last item on my itinerary after several conferences, and let’s just say the return trip is an ongoing dumpster fire. EdgeFest itself was long, because the team that works on the Spock extension decided to get together and get some actual work done before festivities and other requisite meetings.

I’ve finally gotten tired of maintaining my own mail server. I’ve been maintaining it since 1999 in one way or another, and I think it’s just time to take it behind the shed and put it out of my misery.

As to how I reached this decision and what I intend to do about it, well… that’s a story.

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 “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.