PostgreSQL - The Elephant in the room...

[jsobell]

I have to wonder how many people out there have disregarded Umbraco due to it's singular relational database server support.
If you're not running on Azure you are unlikely to want to use SQL Server as your backend database due to its costs, and PostgreSQL has become by far the most popular for new developments (with 49% overall in 2024's Stack Overflow survey) and even PetaPoco now supports PostgreSQL.
Is there a good reason why we're not offering it? In the entire discussion history here on Github I can only see three mentions of Postgres, which seems astonishing given that it is such a popular database.
There was a thread with a pull request three years ago, where someone asked for minor changes to allow a converted Postgres provider, but that PR and the repository have vanished, possibly due to lack of interest or support?
I ask because I have a PostgreSQL based existing system I was hoping to incorporate Umbraco into, but don't want to have to spin up a SQL Server instance just to store Umbraco's extensive user information in a secure manner, and I cannot believe I am the only person with this type of requirement.
Am I missing something?

[jsobell]

Oh, I found the PR and feedback: #13277 with the comment "we can take inspiration from here once this becomes a priority for us again".
Is this really a low priority, and are the changes for .NET9 more important than supporting the most popular databases used by developers? I know which of these I would vote for.