PostgreSQL VS MariaDB

While both Postgres and ClickHouse serve different purposes, the key distinction lies in how they handle replication and sharding. Postgres is primarily designed for transactional workloads (OLTP), where data consistency and durability are prioritized. On the other hand, ClickHouse is tailored for analytical workloads (OLAP), and optimized for high-speed querying and large-scale data analysis.

For your information, the tuplesort.c module flags when the Sort algorithm will use disk by setting the state to SORTEDONTAPE at this line. Disk interactions is handled by the logtape.c module.

This error happens when using a relational database, like PostgreSQL (one of the most popular, and advanced open-source SQL databases on the market).

This tutorial is going to use Postgres for its database because it is well battle-tested, but you're going to use the Prisma ORM to abstract away the database layer. This gives you the flexibility to use a variety of databases, and simplifies the API that you use to interact with it.

Yes, it's a balancing act. I think it's better to have safer defaults here, not prioritizing extra performance. People who are concerned with performance to the degree where checksums would matter need to consult configuration anyway (in many aspects, not only this one) and can disable this specific thing easily.

For the reference, change is in https://github.com/postgres/postgres/commit/04bec894a04c (so should land in PostgreSQL 18 in a year, unless it will get reverted for some reason).

PostgreSQL, commonly referred to as Postgres, is a powerful, open-source relational database management system (RDBMS) known for its robustness, extensibility, and standards compliance. It was introduced in 1986 by Michael Stonebraker and his team at the University of California, Berkeley, as part of the POSTGRES project, which aimed to address some of the limitations of existing database systems at the time.

PostgreSQL: An open-source object-relational database management system, used early on by Uber.

PostgreSQL

Link: https://www.postgresql.org/

When building web applications, authentication is almost always a core requirement. I needed something simple and secure that would let me get started quickly on new projects without over-complicating the setup. My goal was to have a solution that's easy to implement, handles email verification out of the box, and just works. In this post, I'm sharing how to build a straightforward magic link authentication system using Next.js, Auth.js, Prisma, PostgreSQL, and Resend. It's a powerful yet simple solution that accomplishes exactly what I needed, and I hope it'll be useful for your projects too.

One of the most famous examples is MariaDB, a fork of MySQL. When Oracle acquired MySQL back in 2009, concerns arose about the future of the database under a corporate umbrella and while MySQL has remained open source, the idea of it living under Oracle's roof was enough to push some of the original creators to fork an alternative that still lived within the developer community. During the early stages of MariaDB, it was used as a drop-in replacement that promised to remain open and community-driven. Being able to simply switch from MySQL to MariaDB with minimal effort made adopting their product easy. Fast forward to today, MariaDB is widely adopted and continues to evolve independently from its ancestor. With the community driving the success, MariaDB has been adopted as the default database in major Linux distributions, including Debian, RHEL, CentOS, openSUSE, and Fedora.

SQLite is a lightweight database engine written in C. It is a simple, fast, and fully featured implementation of an SQL Database Management System. SQLite differs from other relational databases like MariaDB and PostgreSQL because it does not run as a server.

MariaDB: A fork of MySQL developed by early MySQL employees.

It seems easy enough to just deploy a MySQL container and use it, right? Well... It seems that there are some concerns about its licensing and development direction ever since the brand has been bought by Oracle (remember OpenOffice?). That was the motivation for the MariaDB fork, distributed under the GPLv2 license, which nowadays is not even a 100% drop-in replacement for MySQL, but still works for our case

(At first we're using a PostgreSQL image from the official DockerHub repository, but different databases such as MySQL/MariaDB or MongoDB will follow a similar pattern)

MariaDB is an open-source RDBMS that originated as a fork of MySQL. It aims to maintain compatibility with MySQL while offering additional features.

In a landscape filled with open-source and commercial relational databases, this article focuses on the four most prominent open-source databases - PostgreSQL, MySQL, MariaDB, and SQLite. These DBMS are the most preferred databases per the SO’s 2023 survey.

MariaDB

MariaDB [1] is a community developed fork of MySQL, so you can feel free to use that in place of MySQL.

Another alternative would be Percona [2] which is a drop-in replacement for Oracle MySQL.

About PostgreSQL I haven't had that much of personal experience with it, but for sure I plan to learn it, because it has been battle-tested for years with lots of well-known projects, such as Django framework, for instance.

[1] https://github.com/MariaDB/server

[2] https://github.com/percona/percona-server