Warning: Transaction ID Wraparound Can Freeze Your PostgreSQL Server – Here's How to Prevent It
Halloween is near, but there's something scarier in your PostgreSQL server—Transaction ID wraparound.

This is part of the blog series about building a Co-Pilot for DB Ops. The journey starts here. Thesis Fetching data from the system tables (performance schema) is basically a text2sql task. A good text2sql solution should be able to generate high qua...

This is part of the blog series about building a Co-Pilot for DB Ops. The journey starts here. Thesis Running the co-pilot locally, on a local LLM solves a few problems: No cost. Send as many tokens as you want Secured: No need of any extra service...

This is part of the blog series about building a Co-Pilot for DB Ops. The journey starts here. Thesis: The backed of the system can be Postgres. Extensions, such as pg_vectorize, can simplify adding new documents for the tests. Everything is done usi...

This is part of the blog series about building a Co-Pilot for DB Ops. The journey starts here. Thesis: Sending detailed documentation of every column will ensure high quality SQL. Sending a long context, with detailed information about the schema of ...

This is part of the blog series about building a Co-Pilot for DB Ops. The journey starts here. Testing GPT-3.5 as a Copilot: Navigating Uncharted Territory In software testing, we usually have clear plans for testing regular programs. But trying out ...

TLDR 🗺 In this series of posts I'll write about a long journey to build a Co-Pilot for DB Operations. In the first post I wrote about what is a Co-Pilot for DB Ops, the main motivation and the guidelines for building the tool. In this post I want...