port in config file not respected

Question

port in config file not respected

gsmcwhirter opened this issue 4 years ago · comments

I have a non-standard port for a postgres server and specifying it in the tern.conf file did not pass it through to the connection properly (it still tried to use 5432). Specifying the custom port with --port on the command line did work.

Jack Christensen · Answer 1 · Thu Dec 24 2020 00:39:38 GMT+0800 (China Standard Time)

I believe this was already fixed on master in a9992da but I hadn't tagged a release with it. I've just tagged v1.12.2 which should resolve this issue.

Gregory McWhirter · Answer 2 · Thu Dec 24 2020 10:08:29 GMT+0800 (China Standard Time)

Seems to work with the v1.12.2, thanks. (side note, the v1.12.2 binary reports its version as 1.12.3 with tern version -- not a big deal, just something odd)

Jack Christensen · Answer 3 · Fri Dec 25 2020 00:10:34 GMT+0800 (China Standard Time)

Whoops. I made a typo on the version number. I just tagged v1.12.3 to fix the mismatch. No other changes.