Life with Open Source

commit   : 19f20081df059fef87e14c8e953669bd173dd7f1    
  
author   : Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 15 Oct 2018 17:12:02 -0400    
  
committer: Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 15 Oct 2018 17:12:02 -0400    

commit   : db9034bf7653fa527e2531e1a713dbbd37066a6b    
  
author   : Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 15 Oct 2018 14:01:38 -0400    
  
committer: Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 15 Oct 2018 14:01:38 -0400    

commit   : bc7462d86d3529712cf7c196a04f7d6f8dd8ee34    
  
author   : David Steele <david@pgmasters.net>    
date     : Fri, 31 Aug 2018 13:19:43 -0400    
  
committer: David Steele <david@pgmasters.net>    
date     : Fri, 31 Aug 2018 13:19:43 -0400    

Bug Fixes:  
  
* Fix issue where relative links in $PGDATA could be stored in the backup with the wrong path. This issue did not affect absolute links and relative tablespace links were caught by other checks. (Reported by Cynthia Shang.)  
* Remove incompletely implemented online option from the check command. Offline operation runs counter to the purpose of this command, which is to check if archiving and backups are working correctly. (Reported by Jason O'Donnell.)  
* Fix issue where errors raised in C were not logged when called from Perl. pgBackRest properly terminated with the correct error code but lacked an error message to aid in debugging. (Reported by Douglas J Hunley.)  
* Fix issue when a boolean option (e.g. delta) was specified more than once. (Reported by Yogesh Sharma.)  
  
Features:  
  
* Allow any option to be set in an environment variable. This includes options that previously could only be specified on the command line, e.g. stanza, and secret options that could not be specified on the command-line, e.g. repo1-s3-key-secret.  
* Exclude temporary and unlogged relation (table/index) files from backup. Implemented using the same logic as the patches adding this feature to PostgreSQL, 8694cc96 and 920a5e50. Temporary relation exclusion is enabled in PostgreSQL ≥ 9.0. Unlogged relation exclusion is enabled in PostgreSQL ≥ 9.1, where the feature was introduced. (Contributed by Cynthia Shang.)  
* Allow arbitrary directories and/or files to be excluded from a backup. Misuse of this feature can lead to inconsistent backups so read the --exclude documentation carefully before using. (Reviewed by Cynthia Shang.)  
* Add log-subprocess option to allow file logging for local and remote subprocesses.  
* PostgreSQL 11 Beta 3 support.  
  
Improvements:  
  
* Allow zero-size files in backup manifest to reference a prior manifest regardless of timestamp delta. (Contributed by Cynthia Shang.)  
* Improve asynchronous archive-get/archive-push performance by directly checking status files. (Contributed by Stephen Frost.)  
* Improve error message when a command is missing the stanza option. (Suggested by Sarah Conway.)  

commit   : e0fb7a2ce39f25cbbbe50c95aebdab1ee3beff23    
  
author   : Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 6 Aug 2018 16:13:40 -0400    
  
committer: Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 6 Aug 2018 16:13:40 -0400    

commit   : 50043c87dfaf8e554e792df15ae8ef1fc5df9632    
  
author   : Peter Eisentraut <peter_e@gmx.net>    
date     : Mon, 6 Aug 2018 19:30:02 +0200    
  
committer: Peter Eisentraut <peter_e@gmx.net>    
date     : Mon, 6 Aug 2018 19:30:02 +0200    

commit   : 895fb6e2e270654b2a89042ddaf7db0e1a29003c    
  
author   : Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 6 Aug 2018 16:11:24 -0400    
  
committer: Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 6 Aug 2018 16:11:24 -0400    

commit   : 1af8bbe9abab91b2f269cc6dddcc9b7e5350929d    
  
author   : Peter Eisentraut <peter_e@gmx.net>    
date     : Mon, 6 Aug 2018 19:31:39 +0200    
  
committer: Peter Eisentraut <peter_e@gmx.net>    
date     : Mon, 6 Aug 2018 19:31:39 +0200    

commit   : 2a37ee373aad7f8a702601b1c0bc0df6c79cff58    
  
author   : Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 6 Aug 2018 16:09:28 -0400    
  
committer: Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 6 Aug 2018 16:09:28 -0400    

commit   : 10e1a4a26cb7f849fabd0302b9aec8de9be39be7    
  
author   : Peter Eisentraut <peter_e@gmx.net>    
date     : Mon, 6 Aug 2018 19:35:42 +0200    
  
committer: Peter Eisentraut <peter_e@gmx.net>    
date     : Mon, 6 Aug 2018 19:35:42 +0200    

commit   : ca3489e768990e32096f0f24d46d5f0b8b70cff4    
  
author   : Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 6 Aug 2018 16:07:43 -0400    
  
committer: Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 6 Aug 2018 16:07:43 -0400    

commit   : d275672f7d9ad12b882687debeed549ab5ad0251    
  
author   : Peter Eisentraut <peter_e@gmx.net>    
date     : Mon, 6 Aug 2018 19:44:29 +0200    
  
committer: Peter Eisentraut <peter_e@gmx.net>    
date     : Mon, 6 Aug 2018 19:44:29 +0200    

commit   : 4191e37a9a1fb598267c445c717914012d9bc423    
  
author   : Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 6 Aug 2018 16:05:31 -0400    
  
committer: Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 6 Aug 2018 16:05:31 -0400    

commit   : 4ae11214238b382242c038566e5da970fbdaa355    
  
author   : Peter Eisentraut <peter_e@gmx.net>    
date     : Mon, 6 Aug 2018 20:03:55 +0200    
  
committer: Peter Eisentraut <peter_e@gmx.net>    
date     : Mon, 6 Aug 2018 20:03:55 +0200    

commit   : a8143ec1253f3d9187c053def0b8c515d4f13fd5    
  
author   : David Steele <david@pgmasters.net>    
date     : Thu, 5 Jul 2018 20:16:41 -0400    
  
committer: David Steele <david@pgmasters.net>    
date     : Thu, 5 Jul 2018 20:16:41 -0400    

IMPORTANT NOTE: This release fixes a critical bug in the backup resume feature. All resumed backups prior to this release should be considered inconsistent. A backup will be resumed after a prior backup fails, unless resume=n has been specified. A resumed backup can be identified by checking the backup log for the message "aborted backup of same type exists, will be cleaned to remove invalid files and resumed". If the message exists, do not use this backup or any backup in the same set for a restore and check the restore logs to see if a resumed backup was restored. If so, there may be inconsistent data in the cluster.  
  
Bug Fixes:  
  
* Fix critical bug in resume that resulted in inconsistent backups. A regression in v0.82 removed the timestamp comparison when deciding which files from the aborted backup to keep on resume. See note above for more details. (Reported by David Youatt, Yogesh Sharma, Stephen Frost.)  
* Fix error in selective restore when only one user database exists in the cluster. (Fixed by Cynthia Shang. Reported by Nj Baliyan.)  
* Fix non-compliant ISO-8601 timestamp format in S3 authorization headers. AWS and some gateways were tolerant of space rather than zero-padded hours while others were not. (Fixed by Andrew Schwartz.)  
  
Features:  
  
* PostgreSQL 11 Beta 2 support.  
  
Improvements:  
  
* Improve the HTTP client to set content-length to 0 when not specified by the server. S3 (and gateways) always set content-length or transfer-encoding but HTTP 1.1 does not require it and proxies (e.g. HAProxy) may not include either. (Suggested by Adam K. Sumner.)  
* Set search_path = 'pg_catalog' on PostgreSQL connections. (Suggested by Stephen Frost.)  

commit   : f738d268fec21cb697eb460b82240f2c2b0833f5    
  
author   : David Steele <david@pgmasters.net>    
date     : Thu, 5 Jul 2018 18:36:34 -0400    
  
committer: David Steele <david@pgmasters.net>    
date     : Thu, 5 Jul 2018 18:36:34 -0400    

IMPORTANT NOTE: This release fixes a critical bug in the backup resume feature. All resumed backups prior to this release should be considered inconsistent. A backup will be resumed after a prior backup fails, unless resume=n has been specified. A resumed backup can be identified by checking the backup log for the message "aborted backup of same type exists, will be cleaned to remove invalid files and resumed". If the message exists, do not use this backup or any backup in the same set for a restore and check the restore logs to see if a resumed backup was restored. If so, there may be inconsistent data in the cluster.  
  
Bug Fixes:  
  
* Fix critical bug in resume that resulted in inconsistent backups. A regression in v0.82 removed the timestamp comparison when deciding which files from the aborted backup to keep on resume. See note above for more details. (Reported by David Youatt, Yogesh Sharma, Stephen Frost.)  
* Fix non-compliant ISO-8601 timestamp format in S3 authorization headers. AWS and some gateways were tolerant of space rather than zero-padded hours while others were not. (Fixed by Andrew Schwartz.)  
* Fix directory syncs running recursively when only the specified directory should be synced. (Reported by Craig A. James.)  
* Fix --target-action and --recovery-option options being reported as invalid when restoring with --type=immediate. (Reported by Brad Nicholson.)  
* Fix archive-copy throwing "path not found" error for incr/diff backups. (Reported by yummyliu, Vitaliy Kukharik.)  
* Fix failure in manifest build when two or more files in PGDATA are linked to the same directory. (Reported by Vitaliy Kukharik.)  
* Fix delta restore failing when a linked file was missing.  
* Fix error in selective restore when only one user database exists in the cluster. (Fixed by Cynthia Shang. Reported by Nj Baliyan.)  
  
Improvements:  
  
* Improve the HTTP client to set content-length to 0 when not specified by the server. S3 (and gateways) always set content-length or transfer-encoding but HTTP 1.1 does not require it and proxies (e.g. HAProxy) may not include either. (Suggested by Adam K. Sumner.)  
* Improve performance of HTTPS client. Buffering now takes the pending bytes on the socket into account (when present) rather than relying entirely on select(). In some instances the final bytes would not be flushed until the connection was closed.  
* Improve S3 delete performance. The constant S3_BATCH_MAX had been replaced with a hard-coded value of 2, probably during testing.  
* Make backup/restore path sync more efficient. Scanning the entire directory can be very expensive if there are a lot of small tables. The backup manifest contains the path list so use it to perform syncs instead of scanning the backup/restore path. Remove recursive path sync functionality since it is no longer used.  

commit   : f7123c1bbf239814b33ddc97e53b472cf0e69d16    
  
author   : David Steele <david@pgmasters.net>    
date     : Tue, 22 May 2018 19:53:25 -0400    
  
committer: David Steele <david@pgmasters.net>    
date     : Tue, 22 May 2018 19:53:25 -0400    

Bug Fixes:  
  
* Fix potential buffer overrun in error message handling. (Reported by Lætitia.)  
* Fix archive write lock being taken for the synchronous archive-get command. (Reported by Uspen.)  
  
Improvements:  
  
* Embed exported C functions and Perl modules directly into the pgBackRest executable.  
* Use time_t instead of __time_t for better portability. (Suggested by Nick Floersch.)  
* Print total runtime in milliseconds at command end.