pgkit
blog
| pgkit | blog | |
|---|---|---|
| 7 | 11 | |
| 28 | 9 | |
| - | - | |
| 7.5 | 6.0 | |
| 7 months ago | 3 months ago | |
| Python | ||
| MIT License | Creative Commons Zero v1.0 Universal |
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.
pgkit
- Versioning data in Postgres? Testing a Git like approach
- A PostgreSQL Docker container that automatically upgrades PostgreSQL
- [🅿🅶🅺🅸🆃] Pgkit - Postgres Backup, PITR and recovery management made easy
-
[🅿🅶🅺🅸🆃] Pgkit - Backup, PITR and recovery management made easy
Check the demo: https://github.com/SadeghHayeri/pgkit
blog
- Versioning data in Postgres? Testing a Git like approach
-
A Different Type of SQL Recursion with PostgreSQL
Originally published at https://github.com/vb-consulting/blog/discussions/1
A follow up on this article was written today
[Recursion with PostgreSQL, Follup 1, Perfomances](https://github.com/vb-consulting/blog/discussions/4)
-
Recursion with PostgreSQL Follow-Up 3 - Finding the Right Path
In my previous article, I managed to get some really crazy performances in tree processing by using PostgreSQL recursive procedural-style function.
- Recursive Hierarchical Queries in SQL: A Deep Dive into Employee Level
- Which Way .NET Developer?
-
Recursion with PostgreSQL, Follup 1, Perfomances
I wrote a follow-up on yesterday's article on tree processing and recursion with PostgreSQL. This one: https://github.com/vb-consulting/blog/discussions/1
SQL was never intended for this kind of stuff; I'm sure that Fabian Pascal will tell us all about it.
And indeed, recursive CTEs are awful, confusing, and severely limited ... but they look cool and smart, and smart people use them (I hate them).
In any case, I used a procedural approach to this problem and, with a few smart optimizations, managed to squeeze some really spectacular performances (757K tree records with 20K unique nodes in just 5 seconds without any indexes, so it probably can go even faster).
What are some alternatives?
docker-postgres-upgrade - a PoC for using "pg_upgrade" inside Docker -- learn from it, adapt it for your needs; don't expect it to work as-is!
Logidze - Database changes log for Rails
pgreplay - pgreplay reads a PostgreSQL log file (*not* a WAL file), extracts the SQL statements and executes them in the same order and relative time against a PostgreSQL database cluster.
Architecture-of-consoles - Technical articles about console architecture
PostgreSQL-Disaster-Recovery-With-Barman - A complete end-end project that demonstrates the 'Traditional backup with WAL streaming' architecture implementation (Backup via rsync/SSH + WAL streaming). This is chosen as it provides incremental backup/restore & a bunch of other features.
developer-handbook - An opinionated guide on how to become a professional Web/Mobile App Developer.
docker-pgautoupgrade - A PostgreSQL Docker container that automatically upgrades your database
aquameta - Web development platform built entirely in PostgreSQL
simonwillisonblog-backup - Backups of the database for simonwillison.net
RssDotnet - A list of my favourite dotnet RSS feeds