Postgres Full-Text Search: A search engine in a database

Re:Postgres Full-Text Search: A search engine in a database by blowski on Tuesday July 27, 2021 @01:03PM (#27974753)

…and created a new one if the projection is only eventually consistent. No free lunches here.

[ Parent | on HN ]

Re:Postgres Full-Text Search: A search engine in a database by zepolen on Tuesday July 27, 2021 @01:14PM (#27974898)

How is that different from running Postgres and Elasticsearch separately?

[ Parent | on HN ]

Re:Postgres Full-Text Search: A search engine in a database by blowski on Tuesday July 27, 2021 @01:23PM (#27975022)

It’s not.

It’s a difference between having separate OLAP and OLTP databases, which is what the parent post suggested.

[ Parent | on HN ]

Re:Postgres Full-Text Search: A search engine in a database by justinclift on Tuesday July 27, 2021 @01:31PM (#27975128)

Probably skill set of staff?

For example, if a place has developed fairly good knowledge of PG already, they can "just" (!) continue developing their PG knowledge.

Adding ES into the mix though, introduces a whole new thing that needs to be learned, optimised, etc.

[ Parent | on HN ]