Merge branch 'master' into v3-experimental

* master:
  Tweak replication test setup
  Properly make it a func init()
  The naming really matters
  Fix the syntax
  Properly make the replication tests skippable on 9.5 and below
  I forgot the tests are 9.6+
  One more try for travis
  Valid YAML helps.
  Dont break old postgres
  Try to fix travis
  Add the ability to set all the fields in the constructor
  Start replication now wraps the sql and returns errors properly
  It should all be unsigned.
  Capitalization
  Add replication stop mechanism
  Add basic logical replication protocol support

README.md

@@ -29,6 +29,7 @@ Pgx supports many additional features beyond what is available through database/
 * Large object support
 * Null mapping to Null* struct or pointer to pointer.
 * Supports database/sql.Scanner and database/sql/driver.Valuer interfaces for custom types
+* Logical replication connections, including receiving WAL and sending standby status updates
 
 ## Performance
 
@@ -72,6 +73,7 @@ Then run the following SQL:
     create user pgx_md5 password 'secret';
     create user " tricky, ' } "" \ test user " password 'secret';
     create database pgx_test;
+    create user pgx_replication with replication password 'secret';
 
 Connect to database pgx_test and run:
 
@@ -104,6 +106,22 @@ If you are developing on Windows with TCP connections:
     host  pgx_test  pgx_pw    127.0.0.1/32 password
     host  pgx_test  pgx_md5   127.0.0.1/32 md5
 
+### Replication Test Environment
+
+Add a replication user:
+
+    create user pgx_replication with replication password 'secret';
+
+Add a replication line to your pg_hba.conf:
+
+    host replication pgx_replication 127.0.0.1/32 md5
+
+Change the following settings in your postgresql.conf:
+
+    wal_level=logical
+    max_wal_senders=5
+    max_replication_slots=5
+
 ## Version Policy
 
 pgx follows semantic versioning for the documented public API on stable releases. Branch ```v2``` is the latest stable release. ```master``` can contain new features or behavior that will change or be removed before being merged to the stable ```v2``` branch (in practice, this occurs very rarely).