There are two main ways to install PostgreSQL on mac OS X.
Homebrew can be installed by running the following command in a terminal:
Installing applications on macOS and OS X computers is easy to do when deploying the apps as packages through the Terminal using the Installer command for quiet deployments across your network. Mac App Store: The Mac will only run apps downloaded from the Mac App Store. Mac App Store and identified developers: When you try to open a new app and it’s not on the list of identified.
Even without becoming an expert in Apple's Terminal app, you can use simple commands to achieve things your Mac won't let you do in any other way. If you're just getting used to Terminal.
/usr/bin/ruby -e '$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)'
If Homebrew is already installed, make sure that it is up to date by running:
brew update
Then ensure there are no conflicts or errors using:
brew doctor
Homebrew is a powerful package manager with many uses, including installing and running postgreSQL. This can be done by typing the following command into a terminal:
Now that postgres is installed the default server can be started by running the command:
This will start up a postgres server hosted locally on port 5432. The server will be run out of the directory /usr/local/var/postgres
.
It can now be accessed by typing the following command:
This will connect to the server and access the postgres database. Once this is done:
The process should look like this:
This shows that the server has been started and can be connected to.
A custom data directory can also be used for a server. To do this, first create a directory to be used as the server location. For example, create a directory called myData in the home directory:
Once the directory is created, the server can be initialized. This means that we configure the directory and add the necessary files to run the server. To do this run the initdb
command as shown:
This will fill the myData directory with files necessary to run the server:
Now that the server is initialized and the log file is created, you can start the server from this directory. To do this use the command and substitute in for the specified values:
The “Data Directory” refers to the directory that was just initialized (in this case myData). The “Log file” is a file that will record server events for later analysis. Generally log files are formatted to contain the date in the file name (e.g. “2018-05-27.log” or “myData-logfile-2018-05-27.log”) and should be stored outside of the database that they are logging so as to avoid unnecessary risks. Log files can be dense to read but are very useful for security and debugging purposes:
The command above will generate a log file like the one shown, start the server, and tie the log file to the server. If a log file is not specified, events will be logged to the terminal:
The server will only start if the port is free. If the default server is running it must first be stopped using the pg_ctl -D /usr/local/var/postgres stop
command:
Once started, it can be connected to the same way as before using:
To run a server through the postgres app, the first step is to download the program. The app can be downloaded on postgresapp.com. Once the app is downloaded and moved into the applications folder, the app can be opened.
Open the Postgres app:
In order to start the server, click the start button.
This will start the server. Details on the server can be found by opening the server settings:
This interface shows all the essential information regarding the server. It also allows the port to be changed very easily. This is useful because multiple PostgreSQL servers can
Note: To change the port in the terminal, the ‘postgres.conf’ file (which can be found in the data directory) must be edited. This looks like the following:
Once the app has been downloaded, command line tools can be used as well. These tools can be accessed by typing:
For example, the ‘postgres’ database on the server can be connected to using the psql tool with postgres as an argument:
Rather than typing out the full path each time however, the path can be added to a file that will allow significantly easier access to the tools, allowing the tools be accessed from any directory on the computer. To do this, the following command can be run in the terminal:
Once this is done, the ‘postgres’ database can be accessed by simply typing:
initdb
Written by: Matthew Layne
Reviewed by: Blake Barnhill , Matt David
Visual Studio Code.app
to the Applications
folder, making it available in the macOS Launchpad.You can also run VS Code from the terminal by typing 'code' after adding it to the path:
$PATH
value to take effect. You'll be able to type 'code .' in any folder to start editing files in that folder.Note: If you still have the old code
alias in your .bash_profile
(or equivalent) from an early VS Code version, remove it and replace it by executing the Shell Command: Install 'code' command in PATH command.
Instead of running the command above, you can manually add VS Code to your path, to do so run the following commands:
Start a new terminal to pick up your .bash_profile
changes.
Note: The leading slash is required to prevent
$PATH
from expanding during the concatenation. Remove the leading slash if you want to run the export command directly in a terminal.
Note: Since zsh
became the default shell in macOS Catalina, run the following commands to add VS Code to your path:
Out of the box VS Code adds actions to navigate in editor history as well as the full Debug tool bar to control the debugger on your Touch Bar:
After upgrading to macOS Mojave version, you may see dialogs saying 'Visual Studio Code would like to access your {calendar/contacts/photos}.' This is due to the new privacy protections in Mojave and is not specific to VS Code. The same dialogs may be displayed when running other applications as well. The dialog is shown once for each type of personal data and it is fine to choose Don't Allow since VS Code does not need access to those folders. You can read a more detailed explanation in this blog post.
VS Code ships monthly releases and supports auto-update when a new release is available. If you're prompted by VS Code, accept the newest update and it will get installed (you won't need to do anything else to get the latest bits).
Note: You can disable auto-update if you prefer to update VS Code on your own schedule.
You can configure VS Code through settings, color themes, and custom keybindings and you will often see mention of the File > Preferences menu group. On a macOS, the Preferences menu group is under Code, not File.
Once you have installed VS Code, these topics will help you learn more about VS Code:
If you are running macOS Mojave version, you may see dialogs saying 'Visual Studio Code would like to access your {calendar/contacts/photos}.' This is due to the new privacy protections in Mojave discussed above. It is fine to choose Don't Allow since VS Code does not need access to those folders.
If VS Code doesn't update once it restarts, it might be set under quarantine by macOS. Follow the steps in this issue for resolution.