postgres-elasticsearch-fdw
tbls
Our great sponsors
| postgres-elasticsearch-fdw | tbls | |
|---|---|---|
| 3 | 6 | |
| 106 | 3,068 | |
| - | - | |
| 4.2 | 8.8 | |
| 29 days ago | 10 days ago | |
| Python | Go | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
postgres-elasticsearch-fdw
- Full-text search engine with PostgreSQL (part 2): Postgres vs. Elasticsearch
-
Postgres Full Text Search vs. the Rest
My experience with Postgres FTS (did a comparison with Elastic a couple years back), is that filtering works fine and is speedy enough, but ranking crumbles when the resulting set is large.
If you have a large-ish data set with lots of similar data (4M addresses and location names was the test case), Postgres FTS just doesn't perform.
There is no index that helps scoring results. You would have to install an extension like RUM index (https://github.com/postgrespro/rum) to improve this, which may or may not be an option (often not if you use managed databases).
If you want a best of both worlds, one could investigate this extensions (again, often not an option for managed databases): https://github.com/matthewfranglen/postgres-elasticsearch-fd...
Either way, writing something that indexes your postgres database into elastic/opensearch is a one time investment that usually pays off in the long run.
-
Lesser Known PostgreSQL Features
I used a foreign data wrapper to query elasticsearch indexes from within postgres.[0]
It pushed alot of complexity down away from higher-level app developers not familiar with ES patterns.
[0]: https://github.com/matthewfranglen/postgres-elasticsearch-fd...
tbls
- FLaNK 25 December 2023
- tbls
- Tools to use to make high level Architecture diagrams
-
Graphviz: Open-source graph visualization software
Autogenerated database documentation is often pretty hit and miss but tbls[1] does a pretty good job in that space. Especially when you comment on your tables, fields, views, functions etc (which is a good habit anyway!) the output is quite useful
[1] https://github.com/k1LoW/tbls
-
Lesser Known PostgreSQL Features
In-database comments combined with something like https://github.com/k1LoW/tbls make for very cheap database documentation.
No affiliation with tbls except that I'm a big fan
-
Recommendations for a CLI-tool to generate DB diagrams?
Check out tbls. You can create a ERD in one command
What are some alternatives?
rum - RUM access method - inverted index with additional information in posting lists
dbmate - :rocket: A lightweight, framework-agnostic database migration tool.
pg-ulid - ULID Functions for PostgreSQL
ksuid - K-Sortable Globally Unique IDs
pgvector - Open-source vector similarity search for Postgres
prisma-client-go - Prisma Client Go is an auto-generated and fully type-safe database client
postgres-elasticsearch-fd
js-id - ID generation for JavaScript & TypeScript Applications
plantuml-syntax - vim syntax file for plantuml
quickwit - Cloud-native search engine for observability. An open-source alternative to Datadog, Elasticsearch, Loki, and Tempo.
mermaid - Generation of diagrams like flowcharts or sequence diagrams from text in a similar manner as markdown