Lars Kanis

It's sad, but build scripts with support for a variety of platforms are rarely straightforward. I don't think we can decrease the number of variables and conditions substantive. The tests...

Now I get it.

Thank you for working on this issue!

Hi @guynaor! After thinking a bit more about this issue, I propose to solve it per #485. That means to rely on the connection startup handling of libpq instead of...

You're right, `PG::Connection#initialize` is no longer called since pg-1.3. I made a change to `PG::Connection` which reactivates the call [here](https://github.com/larskanis/ruby-pg/commit/569f9eedb76cc49b6022f32c76c4cc1ada022eeb) but I'm not convinced, that this change should be merged....

I think it's best to derive `PG::Connection.new` instead of `PG::Connection#initialize`. Also note that there are several alias methods: https://github.com/ged/ruby-pg/blob/master/lib/pg/connection.rb#L684-L687

OK, this is rather unexpected :smile: Which RubyInstaller version did you use? Can you compare 3.0 and 3.1 versions? RubyInstaller-3.1 switched to more modern UCRT runtime, while 3.0 still uses...

Some start menu entries were broken. Current master branch has several fixes to them. I hope that fixes this issue as well. Nevertheless Windows-10 seems to have some own rules...

This issue is still present, but most of the time it can be fixed by updateing to the latest RubyInstaller release. I didn't find a better solution so far, but...

@vin1antme It works - thank you!