Live data from Hacker News

PostgreSQL Rising

wekeroad.com

1–10 of 204 posts

Re: PostgreSQL Rising

#2
I'd love to move away from Oracle to Postgres, I really would. I'm trying to. But for massive amounts of data the partitioning and some other features of Oracle just work better. The partitioning is a huge thing, especially for our data which is partitioned by week then organized according to a hierarchical triangular mesh with bitmapped indexes. This works so well for us (at 8 billion rows) it's silly. MySQL couldn't do this and hacking this into Postgres was sloppy. Stored procedures in Oracle work pretty good as well (especially because of shared memory), but I'm trying to eliminate them as much as possible to try to accommodate other people.

I'm quick to complain about Oracle (especially the fucking cost based optimizer and how it falls back to retarded hash joins for me frequently, leading me to add hints, rewrite SQL or run the tuning advisor), but for it's faults, it does some things pretty well.

That being said, I'm wholeheartedly rooting for Postgres.

Re: PostgreSQL Rising

#3
The complaint that MySQL is by default loosey-goosey with your data is valid, but it's an easy default to change. Here is what happens when you run some of the commands shown in that 'Why Not MySQL?' video on a sanely configured MySQL system by setting SQL_MODE to TRADITIONAL. This mode also allows you to not have dates with zeroes, etc.

    mysql> alter table test change column my_money my_money decimal(2,0);
    Query OK, 2 rows affected (0.03 sec)
    Records: 2  Duplicates: 0  Warnings: 0

    mysql> insert into test values (4,'bar', 100);
    ERROR 1264 (22003): Out of range value adjusted for column 'my_money' at row 1

Re: PostgreSQL Rising

#4
What tool is he using to do the postgres part of that video? I've been looking for a decent postgres gui and can't find one.

EDIT: Navicat it looks like.

One comment, way back int he mists of times (the 90's) MySQL was known as the database that would eat your data. It had a number of data gobbling bugs, as well as no transactions. I'm genuinely surprised how far good marketing and ease of use will go to make a product successful. The postgres guys might learn a bit there. Ease of use will drive a lot of adoption.

Re: PostgreSQL Rising

#5

I'd love to move away from Oracle to Postgres, I really would. I'm trying to. But for massive amounts of data the partitioning and some other features of Oracle just work better. The partitioning is a huge thing, especially for our data which is partitioned by week then organized according to a hierarchical triangular mesh with bitmapped indexes. This works so well for us (at 8 billion rows) it's silly. MySQL couldn'…

> our data which is partitioned by week then organized according to a hierarchical triangular mesh with bitmapped indexes

Sounds like you're getting your money's worth out of Oracle - which is a good thing. For many others (especially those in the .NET world) they use very few of the high end SQL Server stuff.

Re: PostgreSQL Rising

#6
post #4

What tool is he using to do the postgres part of that video? I've been looking for a decent postgres gui and can't find one. EDIT: Navicat it looks like. One comment, way back int he mists of times (the 90's) MySQL was known as the database that would eat your data. It had a number of data gobbling bugs, as well as no transactions. I'm genuinely surprised how far good marketing and ease of use will go to make a produ…

Navicat - it's a great GUI

Re: PostgreSQL Rising

#7
post #3

The complaint that MySQL is by default loosey-goosey with your data is valid, but it's an easy default to change. Here is what happens when you run some of the commands shown in that 'Why Not MySQL?' video on a sanely configured MySQL system by setting SQL_MODE to TRADITIONAL. This mode also allows you to not have dates with zeroes, etc. mysql> alter table test change column my_money my_money decimal(2,0); Query OK,…

Yep - easy to alter the defaults. My point was that these are the defaults which I consider silly.

Re: PostgreSQL Rising

#8
post #4

What tool is he using to do the postgres part of that video? I've been looking for a decent postgres gui and can't find one. EDIT: Navicat it looks like. One comment, way back int he mists of times (the 90's) MySQL was known as the database that would eat your data. It had a number of data gobbling bugs, as well as no transactions. I'm genuinely surprised how far good marketing and ease of use will go to make a produ…

pgadmin
Post reply on HN