Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

PostgreSQL's Imperfections

medium.com

Post reply on HN
Print view View original

1–10 of 139 posts

Re: PostgreSQL's Imperfections

#2

Post by osrec »

Not sure if this makes sense, however, I've always preferred MariaDB to Postgres because it feels lighter. And I haven't really come up against any significant limitations in MariaDB that would make me want to switch to Postgres.

Re: PostgreSQL's Imperfections

#3

Post by jeffdavis »

I largely agree, but a couple points I'd like to challenge:

Is hardware corruption really happening and making it into the WAL stream with checksums on?

The next point, on planner hints: it's really just something that hasn't been done. If a few engineers made plans to tackle the problem, a lot could be done in a couple releases' worth of work. In the mean time, people are getting by with various half-measures anyway, such as extensions[1], planner tunables[2], and statistics tweaks[3].

The only dogma is that a half-baked solution isn't wanted. It's got a lot of architectural impact and long-term supportability implications. And a lot of different use cases that need to be considered that may drive different technological solutions. "Make plans stable/managable" is a different use case than "I know something the planner doesn't" which is different from "Make the planner do this thing because I said so".

[1] https://github.com/ossc-db/pg_hint_plan/blob/master/doc/pg_h...

[2] https://www.postgresql.org/docs/current/runtime-config-query...

[3] https://www.postgresql.org/docs/12/sql-createstatistics.html

Re: PostgreSQL's Imperfections

#4

Post by philliphaydon »

osrec wrote: post #2

Not sure if this makes sense, however, I've always preferred MariaDB to Postgres because it feels lighter . And I haven't really come up against any significant limitations in MariaDB that would make me want to switch to Postgres.

Does MariaDB have documentation?

Re: PostgreSQL's Imperfections

#5

Post by osrec »

philliphaydon wrote: post #4
osrec wrote: post #2

Not sure if this makes sense, however, I've always preferred MariaDB to Postgres because it feels lighter . And I haven't really come up against any significant limitations in MariaDB that would make me want to switch to Postgres.

Does MariaDB have documentation?

https://mariadb.com/kb/en/documentation/

Re: PostgreSQL's Imperfections

#6

Post by edoceo »

osrec wrote: post #2

Not sure if this makes sense, however, I've always preferred MariaDB to Postgres because it feels lighter . And I haven't really come up against any significant limitations in MariaDB that would make me want to switch to Postgres.

Heavy writes, mulitstep transactions is where PG has always won for me vs Maria and MySQL - it was even more pronounced when I decided I'm all in on PG c2003

Re: PostgreSQL's Imperfections

#10

Post by DiabloD3 »

jeffdavis wrote: post #3

I largely agree, but a couple points I'd like to challenge: Is hardware corruption really happening and making it into the WAL stream with checksums on? The next point, on planner hints: it's really just something that hasn't been done. If a few engineers made plans to tackle the problem, a lot could be done in a couple releases' worth of work. In the mean time, people are getting by with various half-measures anyway…

Hardware corruption can happen anywhere to anything.

If you care about your data: Use ECC, and use a checksumming filesystem like ZFS, and also on top of this all, export your WALs to a second machine.

Post reply on HN