Thread 105793365

Which one is better in 2025?

Postgres

MariaDB

FoxPro DOS

>>105793365 (OP)
postgres, but for 99% of use cases sqlite is more then enough

>>105795087
What this anon said.

>>105795087
this but replace postgres with MariaDB. he probably made a typo

>>105794174
fuck no. fuck yourself.

>>105793365 (OP)
>PostgreSQL
>"The World's Most Advanced Open Source Relational Database"
>needs a bouncer in front of it otherwise it'll shit it's pants
Why can they just merge the fucking bouncer into it?

1c бyхгaлтepия

>>105793365 (OP)
Do you want a simple but performant db for a mostly read heavy app?
>SQLite

Do you want a simple but performant db for a write heavy app?
>MySQL

Everything else.
>Postgres

>>105795087
This. The default should be to always start with SQLite.

>>105795087
I wish there were a something with datatypes as simple as SQLite.

>>105793365 (OP)
nigger on the right

techlet here. how do apps handle with multiple concurrent attempts to write to an app from the database side of things anyway?

>>105793365 (OP)
sqlite

>>105793365 (OP)
I prefer postgres but sometimes you have to use mysql.

>>105797018
>>105797018
>>105797018
>>105797018
>>105797018
this

>>105798034
>write to an app from the database
You mean read?

MongoDB

>>105797047
Why would you ever choose MySQL over postgres.

>>105798237
WordPress

>>105799215
lmao

>>105798034
Databases are often a source of truth. 99% of the apps want to check the real state of the data from there. Multiple attempts at writing to the same exact data aren't common (i.e. sounds very rare that a bank lets you do the same transaction from two different places logged with the same account) but that's what the ACID principle is for. Usually one transaction trumps the other eventually. And whoever designs the system puts a rollback mechanism or append-only temporary log to review these conflicts, if they ever matter to the bussiness logic.
Think about Google Doc's history but with a bigger dataset. If someone shits over your changes you have a chance to use the history and handpick or even revert them.

>>105799008
No one uses Wordpress in 2025 except pajeets

>>105796214
MariaDB generic error. Installation can't start. Corrupted a system table for no apparent reason. Every database in the server is now inaccessible. Provides no tool to fix a corrupted installation, which shouldn't have happened in the first place.

Quality design(tm). Reliable. Truly, a battle tested RDBMS.

I earnestly recommend it to all serious, non-hobby projects, because it will not fail you at the worst possible time.

>>105799338
Stay in school

>>105799306
That's helpful anon. Thank you.

>>105799471
I have been working in webdev for 10 years

>>105793365 (OP)
My company does Postgres for production and sqlite for dev, I think it's a good strategy

C O L O N I S E D
O
L
O
N
I
S
E
D

>>105793365 (OP)
For me it's MySQL. It just works. Everything supports it. We use it in production at work too.

>>105795087
Than* Learn English.
But you're right.
One thing is for sure there's no use case for MySQL or Mariadb
>>105796214
Absolute dog shit, just like mysql

>>105803757
Garbo, sqlite does all that

>>105804069
We get it, you're unemployed, no need to bring it up constantly.

>>105804577
Sqlite is the most used database system, retard

it doesnt matter at all

Why cant postgres into fast count though

It takes seconds to count a bigish table

>>105793365 (OP)
Lipstick on that guy is super creepy. Why he would do that?

>>105793365 (OP)
I use a custom Javascript sql emulator as a Google webapp api, it stores data in Google sheets with each sheet as a different table.

Postgres
>just use SQLite
what the fuck for? I'm build servers, not single-writer databases.
>it's simpler
nigga if you struggle to work with Postgres then are going to have a horrible time trying to build complex software.
>>105799306
this, conflicts are handled with transactions. make sure to use the correct isolation level (I default to serializable because it makes reasoning about things dead simple, which is the most important attribute when designing concurrent behaviors).
also make sure you have retry logic figured out.
also consider leaving a transaction open as a human makes a decisions based on the state of some data. if this takes too long, then you might need to re-consult data to ensure it has not changed.

>>105793365 (OP)
sqlite

>>105793365 (OP)
Postgres.
But it doesn't matter, what matters is your database scheme. If you design your database like shit, don't expect the RDBMS to bail you out.

For my largest project i use MySQL. Whenever i encountered performance issues, my own retardation was to blame.
Rather than watching database benchmarks, accept your own mistakes and mix them.

It's a tough pill to swallow, because switching the database layout once it's already deployed, is a huge pain.

>>105807289
>Rust troon falls for yet another current-year meme and is heavily invested in "Postgres is just faster because its the current popular opinion that it is"
A few years ago, you would have used MongoDB.
Fun fact: MySQL more performant on scale.

>>105797047
>write heavy
mysql is more focused on reading than writing chud

>>105807436
you talk an awful lot of shit
every database that I interacted with in the medical field was Postgres
imagine paying a license fee to use a database
imagine thinking Mongo would be seen as an alternative to complicated SQL queries
imagine thinking that Rust is a meme

>>105807465
>others use it so it must be good
SQLite is the most used database out there.
MySQL is far more popular than Postgres.
>medical field
>imagine paying a license fee
the irony

Postgres is the current shilled meme, years ago it was MongoDB, when NoSQL was all the rage and SQL was supposed to be old and deprecated.

>>105807489
And MongoDB vanished when they started using the SSPL, which requires corporations to release their Source Code.
Similary, MariaDB is GPL and MySQL i think also GPL but dual licensesd?

While Postgres is a cucked corpo-friendly permissive license.
The only reason why Postgres is shilled, is because big corporations are angry at others being OpenSource.

>>105807465
>imagine paying a license fee to use a database
You mean:
To modify OpenSource software and keeping your modifications ClosedSource.
You should be more specific and say what you want, you fucking corporate bootlicker.

>>105807511
blah blah blah nigga
Postgres is battle tested to shit, has useful features (I use synchronized replication often), and useful extensions (such as PostGIS for querying by geographic data), and just werks
you are the shill here

>>105807531
keep licking the bood of your holy corporation, cuckold

Use inferior products, simply because Mr. Shekelstein needs to keep more secrets.

>>105807531
>Postgres is battle tested to shit
not as much as MySQL though

>>105807540
the fuck does this even mean? you have a big obsession with corporate cock, maybe I could hire you as my secretary one day

>complicated SQL queries
You should not have to do "complicated SQL queries" in the first place.
Rather than doing shit and expecting from the database to eat your shit in the best performance possible... just don't do shit.

>>105807571
t. nocoder

>>105807566
>complains about the license needing payment if you want to change Open Source software and keep your changes Closed Source
>whaaat? What do you mean i am a corpo cuckold? Pfizer uses Postgres, so its good!

>>105807577
Nope.
Just someone who was confronted with "complicated queries" and who had to write 8000 lines of code in the past week to migrate to a different database scheme.

>>105807585
the entire point of a relational database is to allow for complicated queries on data where automatic use of indexes (when determined useful by the query planner) makes shit fast alongside transactions.
if you are trying to tell me that it is poor design to have 5 table joins with various sorts and whatnot, then you do not know what you are talking about.

Ranking from most based to least based:

sqlite > mariadb > mysql > ... > postgres

>>105807612
The Nr.1 performance issue in SQL databases, after missing indexes and retarded choices of types, is when they are used for things that they should not be used for.

The most common argument i see from Postgres corpo shills is that it's better at parsing JSON.
I would say that if you have to parse a JSON in your database, you went massively wrong somewhere.
In fact, that whole argument is emphasizing that Postgres is the new MongoDB. You seem to not even want SQL in the first place...

A relational database is for relational data.

>>105807650
>In fact, that whole argument is emphasizing that Postgres is the new MongoDB. You seem to not even want SQL in the first place...
at no point have I indicated that I am doing retarded shit like what you point out
>A relational database is for relational data.
no shit, and almost all data can be organized relationally.

>>105807671
you are just a puppet repeating what your corpo overlord tells you, literally whining about licenses and about what pharma companies use: >>105807465

So why wouldn't i use you as a stand-in for everything corpo cucks repeat like broken records?

>>105793365 (OP)
My experience as a webshitter working with various systems, old and new:
>sqlite
I love it in theory and it's ideal for local software, but can't recommend it as the DB for a web backend. Even for small MVPs.
It can handle it from a performance standpoint, but it has a lot of quirks and terrible defaults. Types are just suggestions, PKs can be null, foreign keys do nothing until you issue a special pragma telling sqlite to actually enforce them.
It's really easy to fire up a real DB with Docker nowadays, so just do that instead.
>mysql
I've only seen this used with Wordpress and other legacy PHP stuff. To be honest I haven't looked into it recently, newer versions might be fine. It's not on my radar when deciding what DB to use and I don't think anyone would choose it for greenfield now.
>postgres
Basically the default for new projects now.
Has really good extensions for vector similarity search (pgvector with pgvectorscale), so it's an especially attractive option for AI projects that don't want a separate vector DB.
>sql server
It's got a really good UI which is appealing to non-technical/semi-technical management types, and also integrates well with .NET (Entity Framework). Neither of the above are really worth the licensing fee anymore so it's slowly dying off. Last time I checked, no vector features unless you use the Azure cloud version.

>>105793365 (OP)
MariaDB / MySQL

I don't want to VACUUM my database. What am i? A woman?

>>105793365 (OP)
Cute dress

>>105795087
This - sqlite is fine for 99% of apps.

>>105793365 (OP)
PostgreSQL has been better than MySQL for a long time.
>>105793712
>MariaDB
STILL does not support deferred foreign key constraints. That makes it the database equivalent of Rust lang, where you cannot write a safe doubly linked list.
>>105798111
>MongoDB
Not relational.
>>105805512
>Sqlite
For me, it's H2. I can embed the database directly into my Java app sirs.
>>105803757
>MySQL. It just works.
I had a list of gripes about MySQL, but it appears they've fixed a lot in the last few years. They no longer default to MyISAM instead of InnoDB, they no longer default to ISO8859-1 and use UTF8 now, and you can now do case insensitive searches on the UTF8 columns now. But still no deferred FKs, which is a deal breaker.

I still prefer mariadb/mysql but if I wanted to stick a lot of logic in the db I would go for postgres.