Postico offers much more than the ability to query Postgres databases, it comes with the ability to interact with data - filtering rows, sorting rows, editing and even batch editing rows. Postico offers SQL developers a top-notch SQL editor and query interface to Mac users who work with PostgreSQL databases. Our products are designed with a meticulous attention to detail.” We don't care if the competition has more features. This quote from their website explains their philosophy well: They obviously care deeply about user experience. Three brave souls make up the team, and they call Linz, Austria home. They also offer TableTool, an open source CSV editor, and jetread, a tool to let you read Access files from the command line. This small team created Postgres.app (OMG, thank you!) which hands down I found as the easiest way to run PostgreSQL on my Mac. The wonderful people at Egger Apps put out Postico. This helps make sure you don’t forget a key piece of functionality your SQL editor must offer. Take a few minutes and jot down your answers the questions above. Spending a few minutes up front on your requirements can save you hours of frustration. What functionality do I absolutely need? Editing in table results? Query profiling? Advanced database diagramming?.What dev environment do I use? Mac? Windows? Linux?.Do I have to connect locally and remotely?.What databases do I need to connect to? Postgres? MySQL? SQLServer? Access (gasp! Let’s pretend I didn’t say that)? Oracle? SQLite ? Redshift ?.Some questions you’ll want to add to your list: Compiling your must-haves and nice-to-haves before jumping into research can save you hours of time. Things You Should Consider When Choosing a SQL Editorīefore jumping into your research, jot down a few things to consider. I wanted a SQL editor that didn’t crash, that didn’t come stuffed with too much junk, that worked amazing on a Mac, that offered a free version, and that didn’t break the bank.Ī few years later, I can happily report that Postico met each of those challenges and more. I needed a stable, easy-to-use SQL editor that I could quickly connect to local databases and remote databases (usually Postgres databases on Heroku). Needing a SQL Editor, I checked out a bunch, but eventually landed on Postico. Parachuting into the Serenity of Open Source I dove headfirst into Ruby on Rails and Postgres, usually doing all my work in the Heroku world (I love Heroku!). When I parachuted out of that company I didn’t want to fork out thousands of dollars for my dev tools, so I took the plunge into the open source world. I used to dream in SQL in those days, but that’s a story for another day. Quick backstory: many many moons ago I spent most of my days gazing upon SQL Server Management Studio as my SQL editor of choice. Come along with me as I review Postico, a SQL editor specifically designed for PostgreSQL on Macs. Perhaps reading reviews on each would serve you better? Let’s try that instead. Why not choose based on the tried-and-true method of which mascot would win in a fight? Who would walk out of the ring victorious?Ī cat? A beaver? A girl who grows up in the Swiss Alps with her grandfather ? A question for the ages (I personally would vote for the Beaver)! Navicat ? HeidiSQL ? DBeaver ? Postico? You could spend weeks trying them all out. That's all! You now have the exact copy of production database available on your machine.That question spikes anxiety and causes night terrors to crawl up the spines of the best of us. Psql template1 -c 'drop database database_name ' Step 2Ĭreate a new database on the localhost: psql template1 -c 'create database database_name with owner your_user_name Step 3Īnd write your dump into the database: psql database_name < database_name_20160527.sql If you want to use the current localhost database, you must drop it first: If you give no path to the local directory, the dump will be saved in your current working dir.Įxample: scp my_app_database_20160527.sql Restore Your PostgreSQL Dump This command logs you into your remote server using SSH and downloads a given file to the local directory specified by you. Leave SSH and download your new SQL file using SCP. You can name your dump as you wish - I'm using dates to distinguish multiple dumps. Step 2ĭump the desired database: pg_dump database_name > database_name_20160527.sql

The easiest way to check if it's the database to be blamed is to dump the staging/production database and restore it on the localhost.

Oftentimes, when working with the production/staging environments, you may encounter differences with your localhost database setup causing crashes in your app.

Take a postgres dump using postico