Announcement

Collapse
No announcement yet.

PostgreSQL 10.1 Released

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • hansg
    replied
    Originally posted by uid313 View Post
    And it will clutter your system with dozens of executables in /bin or /usr/bin or /usr/sbin.
    It doesn't support the SQL/JSON standard.
    It has a weird, custom, vanity license instead of an established common open source license.
    Most likely does not support the SQL:2016 standard. Probably not even SQL:2011.
    And you post this same bullshit every time a Postgres article is posted, let's not forget that.

    Where files go depends entirely on your chosen OS (see also https://en.wikipedia.org/wiki/Filesy...archy_Standard). If you don't like it, maybe Windows is a better choice for you? On Windows all of Postgres gets installed in a single directory under Program Files.

    Any developer is free to choose the license they like. Why exactly do you believe you have the right to complain?

    And as for standards compliance, the SQL standard is large and complex, and most people really don't care about obscure corner cases.

    This leaves the question of motive. What's your beef with Postgres? It's an amazing database - reliable, fast, full-featured, well-documented, and free. There's nothing else that even comes close.

    Leave a comment:


  • andrei_me
    replied
    Originally posted by uid313 View Post
    And it will clutter your system with dozens of executables in /bin or /usr/bin or /usr/sbin.
    It doesn't support the SQL/JSON standard.
    It has a weird, custom, vanity license instead of an established common open source license.
    Most likely does not support the SQL:2016 standard. Probably not even SQL:2011.
    Non issues compared to data loss at high load that I have faced in the past with MySQL

    Leave a comment:


  • fuzz
    replied
    Originally posted by uid313 View Post
    And it will clutter your system with dozens of executables in /bin or /usr/bin or /usr/sbin.
    It doesn't support the SQL/JSON standard.
    It has a weird, custom, vanity license instead of an established common open source license.
    Most likely does not support the SQL:2016 standard. Probably not even SQL:2011.
    Of course it's not "valid" SQL/JSON. Regardless of anything else, PostgeSQL has supported JSON before it was in the fucking standard.

    Leave a comment:


  • uid313
    replied
    And it will clutter your system with dozens of executables in /bin or /usr/bin or /usr/sbin.
    It doesn't support the SQL/JSON standard.
    It has a weird, custom, vanity license instead of an established common open source license.
    Most likely does not support the SQL:2016 standard. Probably not even SQL:2011.

    Leave a comment:


  • phoronix
    started a topic PostgreSQL 10.1 Released

    PostgreSQL 10.1 Released

    Phoronix: PostgreSQL 10.1 Released

    PostgreSQL 10.1 is now available as the first update over the recently released PostgreSQL 10...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite
Working...
X