Announcement

Collapse
No announcement yet.

PostgreSQL 12 Beta Released With Performance Improvements

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

  • PostgreSQL 12 Beta Released With Performance Improvements

    Phoronix: PostgreSQL 12 Beta Released With Performance Improvements

    Out today is the first beta of the upcoming PostgreSQL 12.0 database server...

    http://www.phoronix.com/scan.php?pag...-Beta-Released

  • #2
    I hope that you can benchmark it Michael compared to v11.x

    Comment


    • #3
      Seems like a really great database. Unfortunately it puts lots of files on the file system like "createuser", etc, very confusing.
      Instead of prefixing all binaries with pg_ or using a pg wrapper script like the "git" and "dotnet" commands does.

      Comment


      • #4
        Originally posted by uid313 View Post
        Seems like a really great database. Unfortunately it puts lots of files on the file system like "createuser", etc, very confusing.
        Instead of prefixing all binaries with pg_ or using a pg wrapper script like the "git" and "dotnet" commands does.
        Use a container, problem solved!

        Comment


        • #5
          Originally posted by uid313 View Post
          Seems like a really great database. Unfortunately it puts lots of files on the file system like "createuser", etc, very confusing.
          Instead of prefixing all binaries with pg_ or using a pg wrapper script like the "git" and "dotnet" commands does.
          Yea it does but remember PostgreSQL was designed originally to see eye to eye with Oracle(IBM DB2, etc.) and many of those annoyances exists to make Oracle(IBM DB2, etc.) migration less painful for DBAs.

          You could give the same reasoning for some of their choices with PLSQL and other toolings

          Comment


          • #6
            Originally posted by hajj_3 View Post
            I hope that you can benchmark it Michael compared to v11.x
            Just saying here, if you need to see benchmarks for PostgreSQL :

            1.) You don't need it, use MySQL instead and save yourself a ton of trouble.
            2.) Any result you get is absolutely useless and probably impossible to reproduce in 99% of the cases that would be useful for anybody that actually need PostgreSQL.

            I don't mean any of this as an insult or anything, i literally mean PostgreSQL is a 10000 heads hydra(like Oracle/DB2/etc.) and literally everything will wildly affect any result, anything from a really simple parameter at postgresql.conf all the way to 1 field type on one of your 10000 tables will make a difference between processing 100 IOPS or 1000000 IOPS this is without actually taking hardware into account which is another massive monster on its own.

            In layman terms:

            MySQL == JavaScript high level framework
            PostgreSQL == low level kernel like C with inline assembly

            Comment


            • #7
              Originally posted by jrch2k8 View Post

              Just saying here, if you need to see benchmarks for PostgreSQL :

              1.) You don't need it, use MySQL instead and save yourself a ton of trouble.
              2.) Any result you get is absolutely useless and probably impossible to reproduce in 99% of the cases that would be useful for anybody that actually need PostgreSQL.

              I don't mean any of this as an insult or anything, i literally mean PostgreSQL is a 10000 heads hydra(like Oracle/DB2/etc.) and literally everything will wildly affect any result, anything from a really simple parameter at postgresql.conf all the way to 1 field type on one of your 10000 tables will make a difference between processing 100 IOPS or 1000000 IOPS this is without actually taking hardware into account which is another massive monster on its own.

              In layman terms:

              MySQL == JavaScript high level framework
              PostgreSQL == low level kernel like C with inline assembly
              Ohhh, what an insult, most common perf pitfalls can be check through analyze.

              When an index is not used, you can check things like default_statistics_target or per column statistics, you check type mismatches or collate used on the column.

              I, for one, dislike MySQL

              Comment


              • #8
                Originally posted by andrei_me View Post

                Ohhh, what an insult, most common perf pitfalls can be check through analyze.

                When an index is not used, you can check things like default_statistics_target or per column statistics, you check type mismatches or collate used on the column.

                I, for one, dislike MySQL
                i mostly agree but once a while ago i knew a badass real PostgreSQL DBA expert and understood that i knew nothing but yeah analyze is the bare basic to fix oblivious performance booboos

                Comment


                • #9
                  Originally posted by jrch2k8 View Post

                  Just saying here, if you need to see benchmarks for PostgreSQL :

                  1.) You don't need it, use MySQL instead and save yourself a ton of trouble.
                  2.) Any result you get is absolutely useless and probably impossible to reproduce in 99% of the cases that would be useful for anybody that actually need PostgreSQL.

                  I don't mean any of this as an insult or anything, i literally mean PostgreSQL is a 10000 heads hydra(like Oracle/DB2/etc.) and literally everything will wildly affect any result, anything from a really simple parameter at postgresql.conf all the way to 1 field type on one of your 10000 tables will make a difference between processing 100 IOPS or 1000000 IOPS this is without actually taking hardware into account which is another massive monster on its own.

                  In layman terms:

                  MySQL == JavaScript high level framework
                  PostgreSQL == low level kernel like C with inline assembly
                  Unless you can't use PostgreSQL because of availability MySQL and it's derivatives are a dumpster fire, I am working on an ETL program transferring stuff from MariaDB that uses MyISAM (Legacy Stuff) to Elasticsearch importing the dataset to PostgreSQL (Unmodified default config) cuts the indexing time down to less than a third. Using an Intel 750 PCIe HD.

                  Comment


                  • #10
                    Originally posted by jrch2k8 View Post

                    Just saying here,
                    ,
                    ... <blah blah> ...

                    In layman terms:

                    MySQL == JavaScript high level framework
                    PostgreSQL == low level kernel like C with inline assembly
                    Nah, sorry. I've been DBA ( and backend dev, and ETL dev ) using both MySQL and Postgres over the years, and while there are differences, it's nothing like you say. Maybe you got in over your head on a Postgres project?

                    Comment

                    Working...
                    X