7 ms·

PostgreSQL 9.0 Final Release Available Now

121 points by mindaugas 16y ago

avar 16y ago
Yesterday's thread discussing 9.0: http://news.ycombinator.com/item?id=1706030 http://news.ycombinator.com/item?id=1706030
mindaugas 16y ago
Full release notes http://www.postgresql.org/docs/9.0/static/release-9-0 http://www.postgresql.org/docs/9.0/static/release-9-0
epi0Bauqu 16y ago
Why use hot-standby over streaming replication or visa-versa?
- gxti 16y ago
  It's a free upgrade from warm standby, whereas SR requires a little more configuration. A good SR cluster also requires that log archiving (warm/hot standby) be set up in case the stream gets behind, otherwise you're at the mercy of whatever happens to be in the master's xlog.
- crad 16y ago
  Hot-Standby: Ability to query against what used to be Warm-Standby boxes which were for disaster recovery only. Streaming Replication: sending log data over sockets instead of relying on shell commands to send logfiles over. They work together to make for happy master-slave replication. It's worth noting this is database server level. Hot-standby copies 100% of a PostgreSQL instance. If you want to replicate individual databases on a server or individual tables in a database, Longdiste, Bucardo or Slony are still the way to go.
ghotli 16y ago
Has anyone been using PostGIS with the RCs? Is it stable and ready for production?
- biog 16y ago
  I use PostGIS with 9.0RC without any problems.
siglesias 16y ago
Can anybody point to a good discussion about the strengths and weaknesses of PostgreSQL relative to MySQL? Or can you weigh in briefly about the tradeoffs between the two? EDIT: Okay, must've touched a few nerves there. Sorry. Question was asked in earnest.
- jacquesm 16y ago
  Of all the flamewar subjects, I think that one is just about the most tried and true one.
  - siglesias 16y ago
    I wasn't trying to start a flamewar! I'm just coding up my first major project and needed help deciding, specifically which one plays better with django.
    - jacobian 16y ago
      If you're using Django, and all else being equal, I'd choose PostgreSQL. Nearly all of the core developers (myself included) use PostgreSQL, so Django tends to have better support and we tend to find (and fix) PostgreSQL-related bugs a little bit quicker. That said, plenty Django sites use MySQL -- including some of the very biggest ones -- without issues. So you're really in good shape either way.
      - deleted 16y ago
        [deleted]
- jacobian 16y ago
  Historically, MySQL has focused on ease of use, speed out-of-the-box, and aimed to be a lightweight, "personal" database (hence the "My"). This fast & light focus meant that certain "BigDB" features (triggers, transactions, ...) fell by the wayside. On the other hand, PostgreSQL has historically focused on correctness and full support for advanced database features, looking to supplant Oracle and SQLServer. This meant that speed and ease of use sometimes suffered. Today, though, both databases have mostly caught up -- MySQL has implemented most of the big ticket features that PostgreSQL had for years, and PostgreSQL (especially with the 9.0 release) has gotten far easier to use and tune, and is now as fast (or faster) than MySQL on most workloads. The heritage still shows, at times: MySQL, even in "strict" mode, still suffers from annoying bugs and mis-interpretations of SQL features. PostgreSQL is still slow out of the box, often needing to be carefully tuned for the best performance. Disclaimer: major PostgreSQL user and fan here. I've tried to give as objective an answer as I can.

121 points by mindaugas 16y ago

avar 16y ago

Yesterday's thread discussing 9.0: http://news.ycombinator.com/item?id=1706030 http://news.ycombinator.com/item?id=1706030

mindaugas 16y ago

Full release notes http://www.postgresql.org/docs/9.0/static/release-9-0 http://www.postgresql.org/docs/9.0/static/release-9-0

epi0Bauqu 16y ago

Why use hot-standby over streaming replication or visa-versa?

gxti 16y ago
It's a free upgrade from warm standby, whereas SR requires a little more configuration. A good SR cluster also requires that log archiving (warm/hot standby) be set up in case the stream gets behind, otherwise you're at the mercy of whatever happens to be in the master's xlog.
crad 16y ago
Hot-Standby: Ability to query against what used to be Warm-Standby boxes which were for disaster recovery only. Streaming Replication: sending log data over sockets instead of relying on shell commands to send logfiles over. They work together to make for happy master-slave replication. It's worth noting this is database server level. Hot-standby copies 100% of a PostgreSQL instance. If you want to replicate individual databases on a server or individual tables in a database, Longdiste, Bucardo or Slony are still the way to go.

ghotli 16y ago

Has anyone been using PostGIS with the RCs? Is it stable and ready for production?

biog 16y ago
I use PostGIS with 9.0RC without any problems.

siglesias 16y ago

Can anybody point to a good discussion about the strengths and weaknesses of PostgreSQL relative to MySQL? Or can you weigh in briefly about the tradeoffs between the two? EDIT: Okay, must've touched a few nerves there. Sorry. Question was asked in earnest.

jacquesm 16y ago
Of all the flamewar subjects, I think that one is just about the most tried and true one.
- siglesias 16y ago
  I wasn't trying to start a flamewar! I'm just coding up my first major project and needed help deciding, specifically which one plays better with django.
  - jacobian 16y ago
    If you're using Django, and all else being equal, I'd choose PostgreSQL. Nearly all of the core developers (myself included) use PostgreSQL, so Django tends to have better support and we tend to find (and fix) PostgreSQL-related bugs a little bit quicker. That said, plenty Django sites use MySQL -- including some of the very biggest ones -- without issues. So you're really in good shape either way.
    - deleted 16y ago
      [deleted]
jacobian 16y ago
Historically, MySQL has focused on ease of use, speed out-of-the-box, and aimed to be a lightweight, "personal" database (hence the "My"). This fast & light focus meant that certain "BigDB" features (triggers, transactions, ...) fell by the wayside. On the other hand, PostgreSQL has historically focused on correctness and full support for advanced database features, looking to supplant Oracle and SQLServer. This meant that speed and ease of use sometimes suffered. Today, though, both databases have mostly caught up -- MySQL has implemented most of the big ticket features that PostgreSQL had for years, and PostgreSQL (especially with the 9.0 release) has gotten far easier to use and tune, and is now as fast (or faster) than MySQL on most workloads. The heritage still shows, at times: MySQL, even in "strict" mode, still suffers from annoying bugs and mis-interpretations of SQL features. PostgreSQL is still slow out of the box, often needing to be carefully tuned for the best performance. Disclaimer: major PostgreSQL user and fan here. I've tried to give as objective an answer as I can.