There may be examples out there, but for me the real problem started when a new user chose PostgreSQL and filed a bug report. And that is not a bug, because a choice for PostgreSQL implies that you need to install a PostgreSQL server, which can have its own dependencies, and can be installed on the same PC, or somewhere else, even on a server running on another OS, and you may even need to tell your firewall that this connection is legitimate. If you don’t, you may have a situation where the server is running, but where Gramps can still not connect to it.
To me this means, that this whole thing is a red herring, because the user should not use that backend at all. And now we’re in a sort of rabbit hole discussing things that are quite interesting by themselves, touching the UI, and our documentation, but at the same time, you won’t get much further if you don’t address the real problem, which is the user making a bad choice.
The next thing is, that I don’t think that you can help anyone on Windows by experimenting with this backend on Fedora, or another Linux, for that matter, for the simple reason that the whole configuration process is quite different. It may give you the same port, if that’s not occupied by Microsoft, but by all other means, I really think that you are wasting your time on this, because there are users with a working PostgreSQL config on Windows 10, here on this forum.
There are more users who completed this than @UlrichDemlehner alone, but you may ask him about this, so that we can use his experience to update the wiki, and maybe some other manual too, like Gramps for seniors. 