tengo
pg_squeeze
Our great sponsors
| tengo | pg_squeeze | |
|---|---|---|
| 1 | 2 | |
| 24 | 401 | |
| - | 2.5% | |
| 6.9 | 8.3 | |
| over 2 years ago | about 2 months ago | |
| Go | C | |
| Apache License 2.0 | GNU General Public License v3.0 or later |
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.
tengo
pg_squeeze
- Pg_squeeze: An extension to fix table bloat
-
PlanetScale Is Now GA
> I am estimating that your database space isn't MySQL, which is just fine of course.
You are absolutely right :) My background is strongly on Postgres, you can see from my profile more information if you want to.
So yes, I apologize if some of my questions are not applying or become to obvious for cases that are MySQL-based. But for the most part, I believe principles of operation are the same.
> [other comments]
As mentioned, thank you very much for the detailed information. This completes the picture that I was looking for. I will definitely go in more detail for some of the links provided.
This principle of operation is not too different from something I proposed to a Postgres project some time ago (https://github.com/cybertec-postgresql/pg_squeeze/issues/18). This tool indeed is conceptually pretty similar. It's a shame that supporting schema changes is not part of their focus at this point. It wouldn't do throttling either, but it shouldn't be a difficult feature to add, I guess.
For other users here that may be interested in the Postgres world, there are two tools that perform similar operation (creating a shadow table and filling it in the background), but are both focused on rewriting the table to avoid bloat, rather than for doing a schema migration:
* pg_repack (https://reorg.github.io/pg_repack/): the most used one, relies on triggers
What are some alternatives?
go-sql-driver/mysql - Go MySQL Driver is a MySQL driver for Go's (golang) database/sql package
gh-ost - GitHub's Online Schema-migration Tool for MySQL
vitess - Vitess is a database clustering system for horizontal scaling of MySQL.
cstore_fdw - Columnar storage extension for Postgres built as a foreign data wrapper. Check out https://github.com/citusdata/citus for a modernized columnar storage implementation built as a table access method.