Enhancement request: PostgreSQL feature and function parity with MySQL

[jk-na]

As much as I love the pixelfed project and very much appreciate the efforts of @dansup and @trwnh (amongst others), the feature and functionality gap between MySQL and PostgreSQL backed instances is widening with each new feature making it difficult to assess progress or recommend the instance to friends and family (my purpose for hosting pf for the past 2+ years).

Of the 10 open issues that I have at least 5 of them are seemingly due to functions or features that work for MySQL failing to work for PostgreSQL. Having looked through the issues list it seems like there are a number of other issues raised by other admins who are also struggling with PostgreSQL related issues.

Is it possible that before the next big feature release, which likely threatens to widen the disparity gap even further, that some efforts are made to to bring postgresql up to feature and function parity with MySQL? After all, it is listed as a supported DB.

The inability to follow any fediverse account (or at least not receive their posts) with any non-lowercase characters in their username is particularly limiting, particularly in relation to the new network timeline feature, though the non-inclusion of posts shared by remote accounts that I follow on timelines on my instance also limits the functionality of said timeline.

My postgresql related issues (though possibly greater than 5 out of 10): #2520 #2721 #2722 #2508 #2726

[jk-na]

Adding another issue to the list: #2904

[xundeenergie]

After the last commit (fixing #2904) searching for upper-case Hashtag does not bring a result. Before i got results...

And even my hashtag Agonitz shows 31 Images found, but presents only 21. Maybe this is also related

[azbulutlu]

these issues apparently broke the third party oauth logins at 11.2. as reported on yunohost side. (YunoHost-Apps/pixelfed_ynh#167)

[orangemelo11]

Comments don’t auto load either on Postgres

[xundeenergie]

Case insensitive search for hashtags is still not working.

[dansup]

Case insensitive/duplicate hashtags on postgres is fixed in #4342

[xundeenergie]

As i commented over there in #4342 there is a a problrm left, using cursor/enter keys.

but... after choosing "#Agontiz" via cursor-keys and pressing <Enter>

and nothing happens.

Klicking on "#Agonitz" opens the search-result-page.