[garciasn]

They’re both great systems but there are a few differences primarily in small ways for most applications:

Maria supports partitioning, Postgres (as of my last knowledge) does not.

Unstructured data is more flexible in Maria natively, but Postgres can support it in a variety of ways.

You can find lists and lists of head to head comparisons out there which will highlight all of the niche differences that each brings over the other.

Ultimately either will work just fine for 99% of use cases.

[floating-io]

> Maria supports partitioning, Postgres (as of my last knowledge) does not.

PostgreSQL's manual indicates that partitioning is a thing[1]. Is the something different than what you're thinking of?

One of my projects has the need to drop millions of rows a month based on the time period, and I've been considering a switch to postgres because they also have a module that will do that automatically.

What am I missing?

[1] https://www.postgresql.org/docs/current/ddl-partitioning.htm...

[justinclift]

> based on the time period

Is it the kind of thing where the TimescaleDB extension would make sense?

https://github.com/timescale/timescaledb

[floating-io]

In my case, pg_partman is actually more than enough. It's just a situation where the data isn't useful after a certain point. Timescale as I understand it would be massive overkill for my situation.

[TkTech]

> Maria supports partitioning, Postgres (as of my last knowledge) does not.

Modern versions of postgres have all the partioning features you'd expect (except automatic ranged partion creation)

[mathnode]

postgres have table partitions now, mariadb can however partition a table over multiple servers or shards using the engines like spider and connect, or proxies like maxscale and proxsql. Local or remote, read your database manual about the fun and caveats that come from partitions.