Skip to content

Commit cb7e27b

Browse files
committed
feat(blog): add Postgres Row-Level Security post (postgres-features #6)
1 parent e7c445a commit cb7e27b

4 files changed

Lines changed: 636 additions & 0 deletions

File tree

  • apps/blog
    • content/blog
      • you-dont-need-to-trust-every-query-postgres-already-has-row-level-security
    • public/you-dont-need-to-trust-every-query-postgres-already-has-row-level-security/imgs

apps/blog/content/blog/you-dont-need-elasticsearch-postgres-already-has-full-text-search/index.mdx

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,7 @@ tags:
1515
series: postgres-features
1616
seriesIndex: 5
1717
prev: you-dont-need-a-job-queue-postgres-already-has-skip-locked
18+
next: you-dont-need-to-trust-every-query-postgres-already-has-row-level-security
1819
---
1920

2021
Postgres ships full-text search in the core server: `tsvector` for indexing text, `websearch_to_tsquery` for parsing what users type, and `ts_rank` for ordering results. For most applications, that is exactly the job [Elasticsearch](https://www.elastic.co/elasticsearch) gets deployed to do. In this post, you'll build ranked, typo-tolerant search on [Prisma Postgres](https://www.prisma.io/docs/postgres), a managed PostgreSQL service, with one generated column, two indexes, and no search cluster to deploy, sync, or pay for.

0 commit comments

Comments
 (0)