Postgresql – Connection timeout errors from Postgres Update Monitor (postgres 9.6)

enterprisedbpostgresql

I am running PostgreSQL 9.6 on windows 10

It seems it has an update monitor that does not use any information about the proxy agent from Windows (we have a corporate proxy). It also does not look at the environment variables HTTP_PROXY or HTTPS_PROXY (which I have set to add credentials via CNTLM for our corporate firewall). This is useful for programs such as NPM and GIT which need to get past our outgoing firewall.

So I am getting the following message every 10 or some minutes as a pop up from a program called:

"D:\Program Files (x86)\postgresql\updatemonitor\bin\UpdManager.exe" --execute  "D:\Program Files\PostgreSQL\9.6\bin\stackbuilder.exe"

The message is very deceiving, but I tracked down the program, and it is the one listed above.

Best Answer

Update Monitor is a little utility from EnterpriseDB that notifies of needed updates. It is not very much documented and doesn't have any obvious way to configure itself. It can be considered non essential, in the sense that the database will perfectly work without it, and you will most probably not miss its functionality.

It's function is explained in the EnterpriseDB website. EDB has also have a Support Page, with contact possibilities that might provide a solution to the malfunction of Update Monitor.

Being a non-essential utility (I've lived without it for very long), if it is giving some annoying popups, I'd consider that the cost versus profit ratio is not favourable, and I'd recommend to, simply, uninstall it. The usual unistall process of any Windows 10 program should be sufficient.

In order to be "up to date" with regard to everything related to PostgreSQL development, it's good to register to the "pgsql-announce@postgresql.org" mailing list from postgresql.org. They'll send one to three emails per week, neat and simple. Any critical update is always announced ASAP.

Related Solutions

Postgresql – Determining the full postgresql size on windows

Part of the difficulty here depends on setup. For this purpose I will assume a default setup. I am also assuming here that we aren't counting system libraries here, or connection libraries, only PostgreSQL itself (i.e. no dependencies, and not libpq).

The best place to start is indeed the sum of the user folder plus the program files/postgresql folder. If you are putting the logs elsewhere you will want to add those in as well.

Postgresql – Postgres pg_basebackup reports directory exists but is not empty

In my opinion it is not related to mklink or Windows issues.

Per pg_basebackup docs, the main data directory will be placed in the target directory, but all other tablespaces will be placed in the same absolute path as they have on the server.

-F format
--format=format

    Selects the format for the output. format can be one of the following:

    p
    plain

    Write the output as plain files, with the same layout as the current data directory and tablespaces. When the cluster has no
    additional tablespaces, the whole database will be placed in the
    target directory. If the cluster contains additional tablespaces, the
    main data directory will be placed in the target directory, but all
    other tablespaces will be placed in the same absolute path as they
    have on the server.

    This is the default format.

Solution: do not run it on the same server, or change backup format.

Best Answer

Related Solutions

Postgresql – Determining the full postgresql size on windows

Postgresql – Postgres pg_basebackup reports directory exists but is not empty

Related Question