Skip to main content

I wanted to post this for everyone who uses VB365 and PGBouncer with Postgres with the recent upgrade 8.1.2.180.

When trying to run this upgrade I ran in to an issue with the following error which was caused by connecting to Postgres via the PBBouncer 6432 port.  I had to stop services, modify the XML files back to 5432 (default PG port) and then run the upgrade.  Once complete I could then revert back to 6432 for PGBouncer and start up the services again.

Error seen during upgrade -

 

@Jim Jones I think we ran into the same thing in our lab deployments.


@Jim Jones I think we ran into the same thing in our lab deployments.

Here is hoping they can fix this for the next patch/update.  😉


I’m not sure if we’ve hard coded the installer to use port 5432 or if this is an issue with some connectivity through PGbouncer (hard to understand if that is the case).  I followed up with my PM colleagues and they are going to have a look.

If anyone is using postgres on an un-upgraded install I would be curious if changing postgres port to 5435 (just something non-standard) had a similar result w/o PGbouncer in the mix.