Indexing Podcast Transcripts in Postgres with Speaker-Turn Metadata
The article argues that podcast transcripts sent to a vector index should store speaker, start time, and episode ID with every chunk, and chunks should never span a speaker-turn boundary. This structure allows retrieval to attribute quotes accurately and gives players a precise timestamp to resume from. It also lets an ingest worker replace a single episode without affecting the rest of the corpus. The author treats chunking as an operational contract, warning that a correction must become searchable as one coherent generation. Turn-based chunking increases record counts, so teams must budget write volume, index size, and delete work accordingly.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in