Life with Open Source

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.  

commit   : ec8e7d60bac23b1b9102798afc30078aca9076ae    
  
author   : Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 7 May 2018 16:59:47 -0400    
  
committer: Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 7 May 2018 16:59:47 -0400    

commit   : 035524b11821343bf1236e8ea5b078b9508225df    
  
author   : Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 7 May 2018 13:13:27 -0400    
  
committer: Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 7 May 2018 13:13:27 -0400    

commit   : 364998df87a8fc498302d4b02681909f81635914    
  
author   : Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 7 May 2018 16:57:35 -0400    
  
committer: Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 7 May 2018 16:57:35 -0400    

commit   : d289dcfc393c5329fb67a1df27957a9923365ce6    
  
author   : Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 7 May 2018 13:13:27 -0400    
  
committer: Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 7 May 2018 13:13:27 -0400    

commit   : ceb2b0b0abaf0e7a14d25c3e75d4fd0b80714149    
  
author   : Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 7 May 2018 16:55:28 -0400    
  
committer: Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 7 May 2018 16:55:28 -0400    

commit   : 23a086a03fe635764c8f0879219a7adeb5a39b56    
  
author   : Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 7 May 2018 13:13:27 -0400    
  
committer: Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 7 May 2018 13:13:27 -0400    

commit   : 2f895f784fb31bf008162e9c52cc0b2c717823e8    
  
author   : Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 7 May 2018 16:53:38 -0400    
  
committer: Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 7 May 2018 16:53:38 -0400    

commit   : e71d9f6951fa61f386bebe3c97735a80def8a1e2    
  
author   : Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 7 May 2018 13:13:27 -0400    
  
committer: Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 7 May 2018 13:13:27 -0400    

commit   : ab5e9caa4a3ec4765348a0482e88edcf3f6aab4a    
  
author   : Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 7 May 2018 16:51:40 -0400    
  
committer: Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 7 May 2018 16:51:40 -0400    

commit   : f5f8b5892a08c678de878653fca906f85e399f27    
  
author   : Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 7 May 2018 13:13:27 -0400    
  
committer: Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 7 May 2018 13:13:27 -0400