Blog: You Don't Need a Vector Database, Postgres Already Has pgvector (series part 3)#8061
Draft
ankur-arch wants to merge 1 commit into
Draft
Blog: You Don't Need a Vector Database, Postgres Already Has pgvector (series part 3)#8061ankur-arch wants to merge 1 commit into
ankur-arch wants to merge 1 commit into
Conversation
…rt 3) Part 3 of the postgres-features series. Covers what embeddings and cosine similarity are, pgvector in raw SQL, and the typed version via @prisma-next/extension-pgvector, with a validated end-to-end demo on a temporary Prisma Postgres database from npx create-db (every command and output comes from a real run against the published 0.14.0 packages). Includes two interactive MDX components (draggable vector-space demo and a 6-step code/terminal runner), a comparison table, FAQ accordions for GEO, an Eclipse-style hero/meta cover, and links the bloom post forward to complete the series chain. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
|
The latest updates on your projects. Learn more about Argos notifications ↗︎
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
New post for the
postgres-featuresseries (part 3, after Redis pub/sub and the bloom index): semantic search in Postgres with pgvector, and the type-safe version via@prisma-next/extension-pgvector.apps/blog/content/blog/you-dont-need-a-vector-database-postgres-already-has-pgvector/— post + two interactive MDX components (VectorSpaceDemo: draggable cosine-similarity plane;PgvectorDemoRunner: 6-step code/terminal walkthrough)apps/blog/public/<slug>/imgs/— hero.svg + meta.png (Eclipse house style, fonts embedded)global.css—.vector-demostyles (the runner reuses the existing.runnerstyles)next:to complete the series chainValidation
@prisma-next/*@0.14.0packages and a freshnpx create-db@latestPrisma Postgres database; every command/output in the post is from a real runtscerrors;cosineDistance→<=>rendering confirmed from extension sourcepnpm types:checkpasses; rendered page verified at/blog/<slug>(demos, FAQ accordions, og:image all present); no newlint:linkserrorsDraft until final read-through.
🤖 Generated with Claude Code