{"componentChunkName":"component---src-templates-post-template-js","path":"/posts/resetting-your-postgres-database/","result":{"data":{"markdownRemark":{"id":"f12704b2-a37b-5d3f-bd3f-af1301a5290b","html":"
\n

\"Postgres

\n
\n

I’ve been using a MacBook for about 2 years now and I honestly can’t count the number of times I’ve encountered this weird Postgres bug:

\n
psql: could not connect to server: Connection refused\n Is the server running locally and accepting\n connections on Unix domain socket "/tmp/.s.PGSQL.5432"?
\n

I’ve solved this quite a number of times but I usually never remember how I resolve it the next time I encounter it. I end up restarting my PC a number of times and having to stack overflow it over and over again.

\n

Today, that changes, I’m going to write about it so I can always come back and check it whenever I run into this problem again.

\n

This issue can be caused by a number of things but usually, it’s when you run brew update and you upgrade your Postgres version that this problem comes up. When this upgrade occurs, your Postgres config file is usually not compatible with the new one. To confirm what the problem is I advise you use this command:

\n
postgres -D /usr/local/var/postgres
\n

This command outputs the logs and you should see the cause of the issue. Here’s what the logs look like on my PC at the time of writing:

\n
2019-02-14 19:15:41.691 WAT [28825] FATAL:  database files are incompatible with server\n2019-02-14 19:15:41.691 WAT [28825] DETAIL:  The data directory was initialized by PostgreSQL version 10, which is not compatible with this version 11.1.
\n

Usually, I don’t have production data or any important database on my PC, I instead have a back up for large dataset I use for testing. So I resolve to reset my PostgreSQL database because I don’t really mind losing the data.

\n

Albeit if you would like to do this quickly with a three-liner and you’re fine with using the default Postgres user, here’s a quick solution— proposed to me by Dawuda Ebenezer.

\n
postgres -D /usr/local/var/postgres\nrm -rf /usr/local/var/postgres && initdb /usr/local/var/postgres -E utf8
\n
# Then start the server:\n$ pg_ctl -D /usr/local/var/postgres -l logfile start (the minor difference I think)
\n

SOLUTION

\n

CLEARING POSTGRES DATA FILES

\n

Let’s start by stopping the Postgres service with the command

\n
brew services stop postgresql
\n

Once this is done, you’d need to delete the data directory for PostgreSQL — L**et me remind you that this is an irreversible action **— if you aren’t sure, use the snippet below to back up the directory

\n
mv `/usr/local/var/postgres/ /usr/local/var/postgres.backup`
\n

You can do this with the snippet below to delete the Postgres data directory:

\n
rm -rf /usr/local/var/postgres/
\n

RESETTING THE DATABASE

\n

Once this is done, you can create a brand new database with the command

\n
initdb /usr/local/var/postgres/
\n

After which you can start the PostgreSQL service with HomeBrew

\n
brew services start postgresql
\n

The action taken above clears all databases saved on the PC. So we need to get started by creating a user, this can be done by entering the PostgreSQL repl with the command:

\n
psql postgres
\n

Now, you should have a new repl instance similar to the screenshot below:

\n
\n

\"Problem

\n
\n

We can then proceed to create a new user with the command

\n
CREATE ROLE username WITH LOGIN PASSWORD 'quoted password';
\n

Remember to add the semi-colon at the end of the command, Postgres can act weird at times when the semi-colon isn’t there.

\n

With the user created, you should be able to log into Postgres now with your credentials.

\n

At this time, the only action we can perform is to log in, because no role has been assigned to the created user. Let’s proceed to assign the user a role, we do that with the command:

\n
ALTER ROLE username CREATEDB
\n

What we’ve done is simply give the created user the ability to create a database. There are other types of roles and you can assign a user multiple roles. The other role types include:

\n\n

Once you’re done assigning roles, you can go on with your day-to-day database activity.

\n

I use Postico for managing my Postgres databases — I personally love the simple and intuitive layout.

\n

Now that the database user was created successfully, I can simply log into PostgreSQL using Postico and manage my database(s). A screenshot of what that looks like is shown below

\n
\n

\"Postico

\n
\n

UPDATE

\n

My solution to this problem is resetting my Postgres database because this mainly occurs in my dev environment which is my PC, albeit, if you would love to retain your data Lawrence Wachira has shared some info on how to go about it. Check the gist and screenshot below

\n
\n

\"Larry's

\n
\n

\n
\n
\n
\n
\n \n\n
\n \n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n
After automatically updating Postgres to 10.0 via Homebrew, the pg_ctl start command didn't work.
The error was "The data directory was initialized by PostgreSQL version 9.6, which is not compatible with this version 10.0."
\n
Database files have to be updated before starting the server, here are the steps that had to be followed:
\n
# need to have both 9.6.x and latest 10.0 installed, and keep 10.0 as default
brew unlink postgresql
brew install postgresql@9.6
brew unlink postgresql@9.6
brew link postgresql
\n
# move 9.6.x db files to another directory
mv /usr/local/var/postgres /usr/local/var/postgres96
\n
# init new database using 10.0
initdb /usr/local/var/postgres -E utf8
\n
# make timezone and timezonesets directories available for 9.6.x installation
mkdir /usr/local/share/postgresql96
cp -r /usr/local/share/postgresql/timezone /usr/local/share/postgresql96
cp -r /usr/local/share/postgresql/timezonesets /usr/local/share/postgresql96
\n
# finally the actual upgrade
# -b is the old binary dir, -B is the new binary dir
# -d is the old data dir, -D is the new data dir
pg_upgrade -b /usr/local/Cellar/postgresql@9.6/9.6.5/bin -B /usr/local/Cellar/postgresql/10.0/bin -d /usr/local/var/postgres96 -D /usr/local/var/postgres
\n
# start 10.0 to check that upgrade works
pg_ctl start -D /usr/local/var/postgres
\n
# cleanup if upgrade was successful
brew uninstall postgresql@9.6
rm -rf /usr/local/var/postgres96
rm -rf /usr/local/share/postgresql96
\n\n\n
\n\n
\n
\n\n
\n
\n view raw\n gistfile1.txt\n hosted with ❤ by GitHub\n
\n
\n

\n

I hope you enjoyed reading this article.

\n

Alternatively, you can check this out:

\n
\n

\"Vincent's

\n
","fields":{"slug":"/posts/resetting-your-postgres-database/","tagSlugs":["/tag/postgres/","/tag/databases/","/tag/sql/","/tag/mac/"]},"frontmatter":{"date":"2019-02-16T12:27:49.850Z","description":"I’ve been using a MacBook for about 2 years now and I honestly can’t count the number of times I’ve encountered this weird Postgres bug: I’ve solved this quite a number of times but I usually never…","tags":["Postgres","Databases","SQL","Mac"],"title":"Resetting your Postgres Database","socialImage":null}}},"pageContext":{"slug":"/posts/resetting-your-postgres-database/"}},"staticQueryHashes":["251939775","401334301","4120999787"]}