Summary
With the growth of vector data as a core element of any AI application comes the need to keep those vectors up to date. When you go beyond prototypes and into production you will need a way to continue experimenting with new embedding models, chunking strategies, etc. You will also need a way to keep the embeddings up to date as your data changes. The team at Timescale created the pgai Vectorizer toolchain to let you manage that work in your Postgres database. In this episode Avthar Sewrathan explains how it works and how you can start using it today.

Announcements

Hello and welcome to the AI Engineering Podcast, your guide to the fast-moving world of building scalable and maintainable AI systems
Your host is Tobias Macey and today I'm interviewing Avthar Sewrathan about the pgai extension for Postgres and how to run your AI workflows in your database

Interview

Introduction
How did you get involved in machine learning?
Can you describe what pgai Vectorizer is and the story behind it?
What are the benefits of using the database engine to execute AI workflows?
- What types of operations does pgai Vectorizer enable?
- What are some common generative AI patterns that can't be done with pgai?
AI applications require a large and complex set of dependencies. How does that work with pgai Vectorizer and the Python runtime in Postgres?
- What are some of the other challenges or system pressures that are introduced by running these AI workflows in the database context?
Can you describe how the pgai extension is implemented?
With the rapid pace of change in the AI ecosystem, how has that informed the set of features that make sense in pgai Vectorizer and won't require rebuilding in 6 months?
Can you describe the workflow of using pgai Vectorizer to build and maintain a set of embeddings in their database?
- How can pgai Vectorizer help with the situation of migrating to a new embedding model and having to reindex all of the content?
How do you think about the developer experience for people who are working with pgai Vectorizer, as compared to using e.g. LangChain, LlamaIndex, etc.?
What are the most interesting, innovative, or unexpected ways that you have seen pgai Vectorizer used?
What are the most interesting, unexpected, or challenging lessons that you have learned while working on pgai Vectorizer?
When is pgai Vectorizer the wrong choice?
What do you have planned for the future of pgai Vectorizer?

Contact Info

Parting Question

From your perspective, what are the biggest gaps in tooling, technology, or training for AI systems today?

Closing Announcements

Thank you for listening! Don't forget to check out our other shows. The Data Engineering Podcast covers the latest on modern data management. Podcast.__init__ covers the Python language, its community, and the innovative ways it is being used.
Visit the site to subscribe to the show, sign up for the mailing list, and read the show notes.
If you've learned something or tried out a project from the show then tell us about it! Email hosts@aiengineeringpodcast.com with your story.
To help other people find the show please leave a review on iTunes and tell your friends and co-workers.

Links

Timescale
pgai
Transformer architecture for deep learning
Neural Networks
pgvector
pgvectorscale
Modal
RAG == Retrieval Augmented Generation
Semantic Search
Ollama
GraphRAG
agensgraph
LangChain
LlamaIndex
Haystack
IVFFlat
HNSW
DiskANN
Repl.it Agent
BM25
TSVector
ParadeDB

The intro and outro music is from Hitman's Lovesong feat. Paola Graziano by The Freak Fandango Orchestra/CC BY-SA 3.0

Psalm 19 - The Importance Of Reading Well

Calvary Monterey Podcast

Introduction

The AI-powered Podcast Player