I installed pgAdmin 4 as part of the postgres installer for Windows. pgAdmin is now telling me there is a newer version (4.8, > 4.5 which I have). However, there is no built in upgrade functionality that I can see, and when I went to download and run the pgAdmin 4 installer to upgrade, it installed itself in the wrong place, leading to problems.
At first I tried installing it to the default location (C:\Program Files (x86)\pgAdmin 4\v4), which was incorrect, because the previous installation (from the postgres installer) went to a different location (C:\Program Files\PostgreSQL\11\pgAdmin 4).
The second time, I pointed it to my existing install of postgres (C:\Program Files\PostgreSQL\11\pgAdmin 4), but it installed itself to a subdirectory there instead (C:\Program Files\PostgreSQL\11\pgAdmin 4\v4), rather than upgrading the existing installation, once again yielding to duplicated installations and problems arising from that. I assume if I go download the postgres installer, it will just reinstall version 4.5 of pgAdmin, though I have not tested this.
What is the correct method for upgrading a pgAdmin instance originally installed by the postgres Windows installer?
I think the best option is to go to Program and files -> Select PostgreSQL and "Uninstall".
Uninstaller will ask you if you want to uninstall the whole application or only individual components. Select individual components and then select pgAdmin.
This will uninstall pgAdmin from PostgreSQL directory.
From now, install the latest version pgAdmin only from official website which will install it into: C:\Program Files (x86)\pgAdmin 4\v4
If you Download the installer from here https://www.postgresql.org/ftp/pgadmin/pgadmin4/v4.8/windows/
It should automatically install the 4.8 version in (C:\Program Files (x86)\pgAdmin 4\v4)
overwriting any existing 4.x version but keeping your server connections and setting.
In your case, the previous install was in a different place, therefore, you ended up having 2 versions.
What I suggest to you is go to control panel and uninstall from there all the versions you have. After that go to the above link, download and install the v4.8 in the default location. Every time there is a new version available just install it and let the installer install it on the default location.
Please note that your pgadmin server connections can be found in %appdata%\pgAdmin.
Note that I have personally just upgraded from v4.5 to v4.8 using this method (installing it in the default location) and it worked like a charm.
Not sure the best approach here.
If you update directly pgadmin from: https://www.postgresql.org/ftp/pgadmin/pgadmin4/v4.10/windows/ the installation goes into
"C:\Program Files (x86)\pgAdmin 4\v4\runtime\pgAdmin4.exe"
Wheras the installation of the whole EnterpriseDB Installer from:
https://www.enterprisedb.com/downloads/postgres-postgresql-downloads is installed here:
"C:\Program Files\PostgreSQL\11\pgAdmin 4\bin\pgAdmin4.exe"
This looks like a wholly undesirable conflict? And leads to the problem identified by #Anomaly ?
To anyone finding this post (like me), before uninstalling your current pgAdmin 4, be aware that there may be limits on compatible versions based on your version of PostgreSQL. Following the instructions by Claudio Corchez, I removed my existing pgAdmin 4 and downloaded the latest 6.15. When I attempted to install it, the installer informed me that this version was not compatible with my version of PostgreSQL 10.3. So, I headed back and downloaded 4.30, which is now running. Unfortunately, it warns me each time I run it that a newer version is available. I just need to upgrade my entire PostgreSQL installation.
I had the same issue previously, and had to manually select the path.
Apparently now (v. 4.25) it auto-detects the path and updates correctly.
I had to download from the website, there was no update button embedded in pgAdmin itself
I am trying to use the old version of 32 bit cygwin (1.7.22 - 1.7.32) which uses GCC 4.7.3 version.
Just found one (cygwin 1.7.25) but during the standard installation (running with setup-x86.exe) it shows the following errors:
The current ini file is from a newer version of setup.exe. If you have
any trouble installing, please download a fresh version from "cygwin
official page"
Is that old version not supported anymore and I can not chose right address from where it can download and install the needed packages?
Thanks,
Arsen
I can't find a good answer. Normally what you see in the installer is what you have access to.
When you load your setup-x86.exe, get to the packages (ignore the warning), and see if you can select the version of Cygwin you need (use the search box to narrow it down). On mine I can only get a few revisions and nothing as old as you need. That being said, I do have the latest installer and can't test this for you.
I'm trying to update node on my Windows 7 box but I'm not seeing the latest version after I re-install/update node.
I'm just going out to http://nodejs.org/download/ and getting the latest Windows installer, v0.10.28. I then just run that installer where it defaults to installing everything on my local hard drive, including npm, which is cool because I wanted to upgrade that as well.
Install runs/finishes with no apparent problem, but when I do a:
node --version
I'm still seeing my "old" version, v0.10.15, not the latest I supposedly just installed, v0.10.28. My npm version still reports my "old" version as well.
I've tried rebooting as well.
How the heck does one update node/npm?
I had a similar problem but on MacOS and the reason was I had nvm installed. So running the commands found on most websites:
sudo npm cache clean -f
sudo npm install -g n
sudo n stable
didn't work, node -v still displayed the old version.
What I did was to install node from nvm:
nvm install v0.12.6
This will build node from scratch on your machine, and then node -v will display the correct version. I think I could have still used the previous commands by using n and then do nvm use v0.12.6, but this is something to test. If you have nvm installed, just check the commands for nvm to upgrade node.
Answer given by Johan Dettmar about using n will work here as well.
For Windows : open command prompt as administrator
For Linux/Mac : sudo -s on terminal
npm cache clean -f (force) clear you npm cache
npm install -g n install "n" (this might take a while)
n stable upgrade to lastest version
Windows Users
Node is most likely installed in 2 locations.
C:\Program Files\nodejs
C:\Program Files (x86)\nodejs
Rename the folder of the (x86) version to "nodejsOLD", restart command prompt, and try again.
node -v
The installer works just fine, things you do NOT need to do:
You do NOT need to uninstall
You do NOT need to reboot
There is a good discussion for Windows and node on stack overflow here:
How do I update npm on Windows?
I had this exact same problem, and one thing to be careful about is to make sure you are downloading the correct architecture version (e.g. 32-bit or 64-bit). When upgrading, I had downloaded the 32-bit version and didn't realize it. But the previous version I had installed was 64-bit. So I actually ended up with a 32-bit and 64-bit version installed. But when you go to do an uninstall, it only lists one version of node.js, so even after I uninstalled, it uninstalled the latest version, but kept the earlier version on there. That's why I kept getting the old version when I did "node -v".
Once I downloaded the correct version (64 bit in my case), the problem was resolved.
A tip that might be useful for others, I found it helpful to known for Windows platforms.
Enter the command in cmd.exe:
where node
This outputted for me that node.exe was in a subdir of Chocolatey.
Problem was that this version was v8.11.1 and it did not work with newer version of the Angular-CLI. So I removed the exe and then ran the installer of the LTS version of Node on Nodejs website to get a working version of Node for Angular. Tested out on Windows 10.
So if you are on Windows, test out the where command in cmd.exe
Linuxers and Mac-ers can use other commands, such as which command.
Screen shot below. I deleted the node.exe file before running the node.exe command.
To fix this problem you can modify your "Environment Variables".
From "System Properties" open the "Environment Variables".
In the system variables section select the path variable and click on the edit button.
In this list you must have the latest folder of installed Node.js(delete other Node.js folders from the list).
That's it
To update Node, download the latest http://nodejs.org/dist/latest/node.exe (or http://nodejs.org/dist/latest/x64/node.exe for 64bit systems) and replace your old node.exe with it.
To update npm, run the npm update npm -g command.
Even though it might sound stupid, make sure you did not previously have node version managers installed which you no longer use, such as Nodist. These will allow the machine to only have their internal node version as the usable version and not the one you install yourself manually.
Uninstalling these package managers, if you want to manually update your Node/NPM versions, will solve the issue.
I had the same problem - but it was caused due too duplicated versions of nodejs being set in my environmental variables.
You can easily check that in Windows using where node in cmd. If more than one path is being output that might be the reason for this error. You can fix it by removing the other environmental variables.
I had the same problem in Windows 10 and none of the above recommendations worked. Then I closed the terminal window, restarted it and the correct version now showed, and the subsequent version errors running other commands also went away. Seems that the version loaded by Windows PowerShell is stuck until the terminal is relaunched. Clearing the cache via command line was futile.
Seems simple and dumb, but that resolved it for me (in the sense that it probably was resolved in the background but I couldn't see the resolution take effect until the terminal was reloaded). Hope this helps someone else.
Using where node, worked for me. That showed me that I had node in the heroku directory as well and since I won't be using that CLI anytime soon, I just removed that dir from the 'path' 'system variable'.
You can fix this on Windows by following these steps if you have already installed nodejs latest version but that is not showing/working.
Open Cmd type where node it will give you a path (like in the
attachment)
Go to that location and delete the node application
exe file
and then come back and try to check that's all you are done , that was the issue of path, your system was using the old reference
I Have installed zeromq 4.0.4 in my ubuntu machine.i have to downgrade my zmq to 3.2.4. i have tried sudo make uninstall , sudo make clean but none of them worked so far. and i also installed 3.2.4 from source. but still my system showing zmq version as 4.0.4. How can i get rid of old zmq files (Clean uninstall of 4.0.4)
Usually you can just use sudo make uninstall if the developer of the package has taken care of making an uninstall target. This is probably not the case for zeromq since you are asking (have not tried myself).
To avoid that kind of problems one way is to use checkinstall instead of make install whenever possible. It will create and install a deb file that can be uninstalled using apt.
make clean Is used to clean the temporary files before building, not to uninstall.
In your situation all you can do, I'm afraid, is to manually remove the files installed by zeromq.
I have recently shifted to OSX environment, so don't know much about MacPorts.
Is there a way to tell MacPorts to pick already installed packages. For instance to install
sudo port install meld
its requiring hell lot of packages, including python2.6. But I already have python2.6 installed.
No there isnt. If you want to link against system installations then use Homebrew or compile manually yourself. Personally i prefer Macports because its completely isolated. Ive got plenty of disk so having duplicates doesnt bother me.