pgAudit 1.0.6 commit log

by Yogesh Sharma
pgAudit
commit log

Bump 9.5 extension version to 1.0.6.

commit   : d0fb52d446ed10cafe304aed16b193c1803cd906    
  
author   : David Steele <david@crunchydata.com>    
date     : Wed, 28 Jun 2017 11:22:01 -0400    
  
committer: David Steele <david@crunchydata.com>    
date     : Wed, 28 Jun 2017 11:22:01 -0400

Click here for diff

The 9.5 version of the extension was accidentally left at 1.0 which does not reflect the various updates. The default is now set to 1.0.6 and an empty update script is included. Run:  
  
alter extension pgaudit update to '1.0.6'  
  
to update the extension version to 1.0.6, though there are no apparent problems with leaving it at 1.0.

M Makefile
A pgaudit–1.0–1.0.6.sql
R094 pgaudit–1.0.sql pgaudit–1.0.6.sql
M pgaudit.control

Vagrantfile for build and regression testing.

commit   : 20b20e0e1000b08ed7e1a3b6f16e86a343a54587    
  
author   : David Steele <david@crunchydata.com>    
date     : Mon, 26 Jun 2017 11:36:33 -0400    
  
committer: David Steele <david@crunchydata.com>    
date     : Mon, 26 Jun 2017 11:36:33 -0400

Click here for diff

A test/Vagrantfile

Demote "extension initialized" message for EXEC_BACKEND builds

commit   : be196bd6a8ce0e10dc6b14cfc747c97a12182701    
  
author   : Joe Conway <mail@joeconway.com>    
date     : Fri, 12 May 2017 10:48:56 -0700    
  
committer: David Steele <david@crunchydata.com>    
date     : Fri, 12 May 2017 10:48:56 -0700

Click here for diff

With EXEC_BACKEND builds, preloading libraries at server start will  
still require each server process to re-load all preload libraries.  
Every time that happens, pgaudit is initialized. The log message  
"pgaudit extension initialized" is thus sent to the postgres log  
for every backend start. This includes autovacuum, which can get  
annoying due to log spam. Fix that by demoting this message to  
DEBUG1 doe EXEC_BACKEND builds, which primarily means Windows  
builds.

M pgaudit.c