From 858eb4bfa659a49f06951cc40c121b0a47b25709 Mon Sep 17 00:00:00 2001
From: Andrei Dziahel <develop7@develop7.info>
Date: Thu, 4 Jul 2019 21:07:17 +0300
Subject: [PATCH] Use pkg-config first, then fall back to pg_config

Since recent releases of PostgreSQL using pg_config for non-server
extensions is discouraged. This is why pg_config gets phased out of
client library development packages.
---
 postgresql-libpq.cabal | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/postgresql-libpq.cabal b/postgresql-libpq.cabal
index e1fe2e5..c3d407e 100644
--- a/postgresql-libpq.cabal
+++ b/postgresql-libpq.cabal
@@ -42,8 +42,8 @@ Custom-setup
 -- If true,  use pkg-config,  otherwise use the pg_config based build
 -- configuration
 Flag use-pkg-config
-  default: False
-  manual:  True
+  default: True
+  manual: False
 
 Library
   hs-source-dirs:      src