postgres

PostgreSQL with extensibility and performance patches (by orioledb)

Postgres Alternatives

Similar projects and alternatives to postgres

  • PostgreSQL

    Mirror of the official PostgreSQL GIT repository. Note that this is just a *mirror* - we don't work with pull requests on github. To contribute, please see https://wiki.postgresql.org/wiki/Submitting_a_Patch

  • orioledb

    OrioleDB – building a modern cloud-native storage engine (... and solving some PostgreSQL wicked problems) Β πŸ‡ΊπŸ‡¦

  • InfluxDB

    Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

    InfluxDB logo
  • Tile38

    Real-time Geospatial and Geofencing

  • buntdb

    BuntDB is an embeddable, in-memory key/value database for Go with custom indexing and geospatial support

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better postgres alternative or higher similarity.

postgres reviews and mentions

Posts with mentions or reviews of postgres. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-07-15.
  • PostgreSQL: No More Vacuum, No More Bloat
    6 projects | news.ycombinator.com | 15 Jul 2023
    > .. 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
    2 projects | /r/PostgreSQL | 25 Feb 2022
    3 projects | news.ycombinator.com | 24 Feb 2022
  • A note from our sponsor - WorkOS
    workos.com | 29 Apr 2024
    The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more β†’

Stats

Basic postgres repo stats
4
23
8.1
about 2 months ago

orioledb/postgres is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.

The primary programming language of postgres is C.


Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com