pg_similarity
pgsentinel
pg_similarity | pgsentinel | |
---|---|---|
3 | 2 | |
352 | 157 | |
- | 1.3% | |
0.0 | 4.7 | |
8 months ago | 20 days ago | |
C | C | |
BSD 3-clause "New" or "Revised" License | PostgreSQL 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.
pg_similarity
-
Data Cleaning in SQL
For Postgres, there is an extension that provides that.
-
Show HN: Supabase Clippy – ChatGPT for Supabase Docs
Note that pgvector isn't supported on any of the large cloud providers' hosted Postgres offerings, other than Supabase. https://github.com/pgvector/pgvector#hosted-postgres has instructions on how to add your voice to request it to be added!
(It does seem that the ancient https://github.com/eulerto/pg_similarity is supported by RDS and Google Cloud - but it's hard to tell whether attention was paid to its performance characteristics with nearly the rigor that pgvector seems to have been designed.)
-
Official Elasticsearch Python library no longer works with open-source forks
While I don't doubt that you know your usecase and weighed/tried the option.
> Postgres search is essentially an easier to use regex engine.
I'm not sure exactly what you meant to convey here, but if you're searching with LIKE or `~` you're not doing Postgres's proper Full Text Search. You should be dealing with tsvectors[0]
> As soon as you need multiple languages
Postgres FTS supports multiple languages and you can create your own configurations[1]
> advanced autocomplete
I'm not sure what "advanced" autocomplete is but you can get pretty fast trigram searches going[2] (back to LIKE/ILIKE here but obviously this is an isolated usecase). In the end I'd expect auto complete results to actually not hit your DB most of the time (maybe I'm naive but that feels like a caching > cache invalidation > cache pushdown problem to me)
> misspelling detection
pg_similarity_extension[3] might be of some help here, but it may require some wrangling.
> large documents, large datasets,
PG has TOAST[4], and obviously can scale (maybe not necessarily great at it) -- see pg_partman/Timescale/Citus/etc.
> custom scoring
Postgres only has basic ranking features[5], but you can write your own functions and extend it of course.
Solr/ES are definitely the right tools for the job (tm) when the job is search, but you can get surprisingly far with Postgres. I'd argue that many usecases actually don't want/need a perfect full text search solution -- it's often minor features that turn into overkill fests and ops people learning/figuring out how to properly manage and scale an ES cluster and falling into pitfalls along the way.
[0]: https://www.postgresql.org/docs/current/textsearch-intro.htm...
[1]: https://www.postgresql.org/docs/current/textsearch-intro.htm...
[2]: https://about.gitlab.com/blog/2016/03/18/fast-search-using-p...
[3]: https://github.com/eulerto/pg_similarity
[4]: https://www.postgresql.org/docs/current/storage-toast.html
[5]: https://www.postgresql.org/docs/9.5/textsearch-controls.html...
pgsentinel
-
[RDS] Huge spikes in CPU Usage, but the Freeable Memory remains high. How do I configure my DB to use more memory?
Another Another source of high CPU could be wait events. There are no built-in tools in Postgres to monitor them (unless RDS provides some). The approach I'd take on a "regular" Postgres installation is to sample the content of pg_stat_activity and then later analyze that after spikes have occurred. There are several extensions that already provide this, e.g. pg_profile or pg_wait_sampling or pgsentinel
-
Any Tips for Analyzing (Concurrent) Transaction Performance?
pgsentinel
What are some alternatives?
git-imerge - Incremental merge for git
plpgsql_check - plpgsql_check is a linter tool (does source code static analyze) for the PostgreSQL language plpgsql (the native language for PostgreSQL store procedures).
elasticsearch-py - Official Python client for Elasticsearch
pg_wait_sampling - Sampling based statistics of wait events
mergify - Merge git changes on commit at a time.
pg_net - A PostgreSQL extension that enables asynchronous (non-blocking) HTTP/HTTPS requests with SQL
git-mergify-rebase - Merge git changes one commit at a time.
pg_profile - Postgres historic workload reports
vasco - vasco: MIC & MINE statistics for Postgres
pg_show_plans - Show query plans of all currently running SQL statements
tds_fdw - A PostgreSQL foreign data wrapper to connect to TDS databases (Sybase and Microsoft SQL Server)
parallel-qo-postgres - (not) Parellel Query Optimizer for Postgres. In this fork of Postgres, we replace the original query optimizer with a parallelized query optimizer based on the work of Trummer et al.