postgres
PostgreSQL
postgres | PostgreSQL | |
---|---|---|
4 | 411 | |
23 | 14,834 | |
- | 2.6% | |
9.6 | 10.0 | |
5 days ago | about 17 hours ago | |
C | C | |
GNU General Public License v3.0 or later | 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.
postgres
-
PostgreSQL: No More Vacuum, No More Bloat
> .. and the delta code to be committed upstream is less than 2K LOC.
Then mainline it?
The last commit that /postgres/postgres and /orioledb/postgres share (1) is 6 months old for 15.2?
I mean, this is literally what I'm pointing out in my comment; you're chasing a moving target. Every change postgres makes, you have to merge in check it doesn't conflict, roll out a new patch set...
...and, you're already falling behind on it.
So, going forward, how do you plan to keep up to date...? ...because it looks to me, like a < 2K LOC isn't a fix for this problem; it hasn't solved it for you, as time goes forwards, it will continue not to be a solution to the problem.
The solution is mainlining those changes --> https://github.com/orioledb/postgres/issues/2
> Currently the changes needed to Postgres core are less than a 1000 lines of code. Due to the separate development schedules for Postgres and OrioleDB, these changes cannot be unstreamed in time for v.15.
^ They were < 1000 lines a year ago, apparently.
I think you can draw a clear pattern in how this going to go, going forward.
[1] - https://github.com/postgres/postgres/commit/78ec02d612a9b690... vs https://github.com/orioledb/postgres/commit/78ec02d612a9b690...
- OrioleDB – solving some PostgreSQL wicked problems
PostgreSQL
-
Essential Tools & Technologies for New Developers
Every time I buy a new computer, the first thing I install is the servers for MySql and Postgres, the two most common databases. This way, I can start the databases with a simple command like this:
- OpenBSD 7.3 を 7.4 へ アップグレード
-
What do you want to watch next? This is why I built GoodWatch.
Data Handling: Utilizes Windmill for data pipelines, with a primary database powered by PostgreSQL. Auxiliary data storage is handled by MongoDB, with Redis for caching to optimize performance
-
System Design: Databases and DBMS
PostgreSQL
- Presentación del Operador LMS Moodle
-
Introducing LMS Moodle Operator
The LMS Moodle Operator serves as a meta-operator, orchestrating the deployment and management of Moodle instances in Kubernetes. It handles the entire stack required to run Moodle, including components like Postgres, Keydb, NFS-Ganesha, and Moodle itself. Each of these components has its own Kubernetes Operator, ensuring seamless integration and management.
-
Integrate txtai with Postgres
Another key feature of txtai is being able to quickly move from prototyping to production. This article will demonstrate how txtai can integrate with Postgres, a powerful, production-ready and open source object-relational database system. After txtai persists content to Postgres, we'll show it can be directly queried with SQL from any Postgres client
-
Understanding SQL vs. NoSQL Databases: A Beginner's Guide
SQL (Structured Query Language) databases are relational databases. They organize data into tables with rows and columns, and they use SQL for querying and managing data. Examples include MySQL, PostgreSQL, and SQLite.
-
From zero to hero: using SQL databases in Node.js made easy
Node.js, MySQL and PostgreSQL servers installed on your machine
-
I Deployed My Own Cute Lil’ Private Internet (a.k.a. VPC)
Each app’s front end is built with Qwik and uses Tailwind for styling. The server-side is powered by Qwik City (Qwik’s official meta-framework) and runs on Node.js hosted on a shared Linode VPS. The apps also use PM2 for process management and Caddy as a reverse proxy and SSL provisioner. The data is stored in a PostgreSQL database that also runs on a shared Linode VPS. The apps interact with the database using Drizzle, an Object-Relational Mapper (ORM) for JavaScript. The entire infrastructure for both apps is managed with Terraform using the Terraform Linode provider, which was new to me, but made provisioning and destroying infrastructure really fast and easy (once I learned how it all worked).
What are some alternatives?
orioledb - OrioleDB – building a modern cloud-native storage engine (... and solving some PostgreSQL wicked problems) 🇺🇦
psycopg2 - PostgreSQL database adapter for the Python programming language
buntdb - BuntDB is an embeddable, in-memory key/value database for Go with custom indexing and geospatial support
ClickHouse - ClickHouse® is a free analytics DBMS for big data
Tile38 - Real-time Geospatial and Geofencing
phpMyAdmin - A web interface for MySQL and MariaDB
Firebird - FB/Java plugin for Firebird
Adminer - Database management in a single PHP file
SQLAlchemy - The Database Toolkit for Python
MariaDB - MariaDB server is a community developed fork of MySQL server. Started by core members of the original MySQL team, MariaDB actively works with outside developers to deliver the most featureful, stable, and sanely licensed open SQL server in the industry.
debezium - Change data capture for a variety of databases. Please log issues at https://issues.redhat.com/browse/DBZ.
MySQL - MySQL Server, the world's most popular open source database, and MySQL Cluster, a real-time, open source transactional database.