Skip to content

feat(blog): add Postgres full-text search post #8093

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nurul3101 merged 1 commit into from
Jul 22, 2026
Merged

feat(blog): add Postgres full-text search post #8093

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions ...ntent/blog/you-dont-need-a-job-queue-postgres-already-has-skip-locked/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,7 @@ tags:
series: postgres-features
seriesIndex: 4
prev: you-dont-need-a-vector-database-postgres-already-has-pgvector
next: you-dont-need-elasticsearch-postgres-already-has-full-text-search
---

Postgres can run a reliable background job queue, and the key is one clause: `FOR UPDATE SKIP LOCKED`. In this post, you'll build a queue with retries and concurrent workers on [Prisma Postgres](https://www.prisma.io/docs/postgres), a managed PostgreSQL service: one table, a handful of short queries, and no message broker to deploy, monitor, or pay for.
Expand Down
Loading
Loading