pgDevOps will help your developers and operations teams work collaboratively, efficiently, and openly.

To understand the value added when you include pgDevOps in your PostgreSQL tool-chain, keep reading.


Go straight to the tutorial to start using pgDevOps today!

Why DevOps: A brief explainer

First a little background to better understand why BigSQL built pgDevops.


“It’s not my machines, it’s your code!”
“It’s not my code, it’s your machines!”
– from Deploys a Day: Dev and Ops Cooperation at Flickr
(and said by everyone)

Sound familiar? This is a common interaction (distraction) between development and operations teams in IT Departments everywhere and everyday. This is because the two roles’ directives are often diametrically opposed. Devs need to respond quickly to changes. Ops must maintain stability.

DevOps: To the rescue

Insanity: doing the same thing over and over again and expecting different results.
– Albert Einstein

In 2008 Andrew Clay Shafer and Patrick Debois first discussed “Agile Infrastructure” at the Agile conference. Soon after, the term “DevOps” was coined as a moniker for the practice of building infrastructure, systems, and a culture to enable cooperation between development and operations teams.

At the Velocity Conference in 2009, John Allspaw and Paul Hammond gave their seminal presentation 10 Deploys a Day: Dev and Ops Cooperation at Flickr where they outlined the 10 key ingredients that would become central to the DevOps philosophy:

devops_logo Tools

  1. Automated infrastructure
  2. Shared version control
  3. One step build and deploy
  4. Feature flags
  5. Shared metrics
  6. IRC and IM robots


  1. Respect
  2. Trust
  3. Healthy attitude about failure
  4. Avoiding blame

Since 2009, DevOps practices have become increasingly popular as businesses require faster time to market to remain competitive.

In fact, DevOps teams increased from 16% in 2014 to 19% in 2015 to 22% in 2016.
– 2016 State of DevOps Report

DevOps ROI

At BigSQL we have seen the benefits of adopting Agile / Lean / DevOps practices. But don’t take our word for it. In the 2016 State of DevOps Report published by Puppet, ROI calculations illustrated savings in millions (and sometimes billions) of dollars annually – illustrated in the tables below pulled from the report:

pgDevOps: The moral of the story is…

To help our colleagues at OpenSCG provide better service to our clients, BigSQL developed pgDevOps – a one stop shop for provisioning and monitoring PostgreSQL databases.


But even more importantly, pgDevOps has helped support a culture of trust and understanding by:

  • eliminating wait times by giving developers the power to standup precompiled PostgreSQL versions on Windows, Linux, and Mac.
  • providing one-click installs from an extensive list of community packages to extend your PostgreSQL capabilities
  • embedding intuitive graphs, metrics, and access to logfiles for monitoring implications of changes to code, queries, and infrastructure
  • providing simple navigation to switch to pgAdmin4 Web conveniently hooked to your PostgreSQL installations
  • incorporating a plProfiler Console to create performance profiles of PL/pgSQL functions and stored procedures and increase efficiency of your code
  • incorporating a pgBadger Console for log analysis

pgDevOps: Get it now!

And now… we are making pgDevOps available to the PostgreSQL community! Try it out by going to our tutorial. Have issues or suggestions? Please let us know at BigSQL Feedback.

pgDevOps will help bring your development and operations teams closer – making them DevOps!

cue the kumbaya music…)