this post was submitted on 11 Jan 2026
348 points (97.5% liked)

Selfhosted

60210 readers
1021 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[โ€“] roguelazer@lemmy.world 7 points 5 months ago* (last edited 5 months ago) (1 children)

MySQL often has moderately higher performance (particularly for workloads where you want your data clustered by PK, which is how InnoDB is natively structured) and its replication system is much more flexible than either of PostgreSQL's. I like Percona personally, but MariaDB is fine too.

[โ€“] msage@programming.dev 0 points 5 months ago

Is it true?

Postgres with correct fillfactor, it doesn't create new pages and works very fast.

Replication in MySQL always sucked ass, only received synchronous replication in some new edition, and that also didn't sound great.

Postgres has logstream and logical replication, both of them can be set to various levels of synchronicity, and logical replication is configurable at least as well as MySQL is in terms of which data is sent.