forked from EnterpriseDB/barman
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathChangeLog
2204 lines (1365 loc) · 74.1 KB
/
ChangeLog
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
2016-02-26 Marco Nenciarini <[email protected]>
Update the ChangeLog file
Prepared version 1.6.0
2016-02-24 Giulio Calacoci <[email protected]>
Fix subtle bug in local recovery
2016-02-20 Marco Nenciarini <[email protected]>
Depend on pytest-runner module only when tests are actually invoked
2016-02-18 Marco Nenciarini <[email protected]>
Enable E501 check (long lines) in flake8
Enabled in flake8 the E501 check, and reformatted text according to the
new line length policy.
Use pytest-runner module to run tests in setup.py
2016-02-18 Leonardo Cecchi <[email protected]>
Fix check if ssh is missing
Catch any 'command not found' errors during ssh check
2016-02-17 Marco Nenciarini <[email protected]>
Update the ChangeLog file
Prepared version 1.6.0b3
2016-02-15 Marco Nenciarini <[email protected]>
Stop running tests on Python 3.2
2016-02-11 Marco Nenciarini <[email protected]>
Make the code compatible with Python >= 3.2
All the incompatible constructs were rewritten to support both Python 2.x
and 3.x. Previously we were running 2to3 during the setup execution.
2016-02-16 Gabriele Bartolini <[email protected]>
Add Leonardo Cecchi to authors
2016-02-15 Leonardo Cecchi <[email protected]>
Rollback transaction after starting a backup
Following the complete refactoring of the PostgreSQL connection code,
part of this 1.6.0 previous versions (alpha1, beta1 and beta2),
Barman is keeping an IDLE connection while taking a backup.
This could trigger spurious alerts if a transaction has been left open.
2016-02-15 Giulio Calacoci <[email protected]>
Fix output of 'barman check --nagios'
Display the correct number of servers with 'barman check --nagios'
2016-02-12 Leonardo Cecchi <[email protected]>
Enhance test coverage for the wal_archiver module
Remove the unused 'is_wal_relevant' method as well.
2016-02-12 Gabriele Bartolini <[email protected]>
Add section about contributing for Barman
Add a section about .partial files in the documentation
2016-02-12 Leonardo Cecchi <[email protected]>
Add 'receive-wal running' check
When `streaming_archiver` is enabled, this check ensures that
a `receive-wal` process is running.
2016-02-12 Giulio Calacoci <[email protected]>
Add --reset option to receive-wal comand
Add the `--reset` option to the `receive-wal` command, allowing
users to reset the WAL location of the streaming archiver.
This is useful in case Barman goes out of sync with the master
server.
2016-02-10 Marco Nenciarini <[email protected]>
Update the ChangeLog file
2016-02-10 Gabriele Bartolini <[email protected]>
Prepared version 1.6.0b2
2016-02-05 Leonardo Cecchi <[email protected]>
Add check for FAILED backups
The 'barman check' command now checks for the presence of failed backups.
2016-02-08 Giulio Calacoci <[email protected]>
Complete integration of RemoteStatusMixin class
Let classes implementing the the get_remote_status method inherit
from the RemoteStatusMixin base class, completing the refactoring
activity started with a previous commit (3179a1e).
2016-02-08 Marco Nenciarini <[email protected]>
Fix unwanted removal of duplicate WAL from archive
This commit removes an unused and dangerous option from the Compressor
interface that allowed the removal of the source WAL file after
compression (introduced in 1.6.0 development branch).
Fixes: #27
Remove trashing of old WAL files from the archiver
The archiver now always archives any file with a valid name that
finds inside the incoming directory.
NOTE: The block of code that has been removed changes behaviour
of existing Barman installations, but in a conservative way.
We defer to future versions of Barman to better understand
WAL files' sequentiality (parsing history files, for example),
by writing specific classes/modules responsible for deeper
and more robust checks in the archive area.
2016-02-05 Marco Nenciarini <[email protected]>
Manage the termination of receive-wal in cron
When the 'streaming_archive' option is disabled for a server,
a cron execution makes sure that a running receive-wal process
is correctly terminated.
Clearer output and logging messages for `receive-wal`.
2016-02-05 Leonardo Cecchi <[email protected]>
Add check for archiver errors
Barman now checks for the presence of files in the error directory.
2016-02-04 Giulio Calacoci <[email protected]>
Improve error handling when required server parameters are missing
Add error handling in case a required parameter (i.e. ssh_command,
conninfo, ...) is missing, by emitting meaningful error messages.
2016-02-02 Giulio Calacoci <[email protected]>
Adjust severity of some messages produced by cron command
The messages about subprocess execution produced by the cron command
were emitted for every cron run. They provide little information and
their presence may make the log difficult to analyse, so they have been
removed from log.
2016-02-02 Aydan <Aydan Tasdemir>
Update docs - Added remote recovery command
Closes: #26
2016-02-01 Marco Nenciarini <[email protected]>
Update the ChangeLog file
Prepared version 1.6.0b1
2016-01-29 Marco Nenciarini <[email protected]>
Fix python 3.2 error on travis-ci
Avoid exceptions during ProcessManager initialization
Previously a LockFileParsingError exception could have been raised if a
lock file were empty.
Also, the LockFile class now writes the lock content atomically
2016-01-28 Giulio Calacoci <[email protected]>
Remove a spurious error when last_failed_wal is a history file
Fixes: SF#77
2016-01-27 Giulio Calacoci <[email protected]>
Fix the 'status' command output with PostgreSQL < 9.4
Make sure only one 'Last archived WAL' line is present.
Fix the command used to retrieve the last archived WAL through
ssh when the pg_stat_archiver view is not available.
Fixes: #25
2016-01-28 Gabriele Bartolini <[email protected]>
Set version to 1.6.0b1
2016-01-21 Giulio Calacoci <[email protected]>
Add --stop option to receive-wal command
Add the option --stop to the receive-wal command, allowing the user to
stop a receive-wal process that running in background for a specific server.
The implementation is based on the new class ProcessManager that will be
used in the future to manage all barman's sub-processes.
2016-01-24 Gabriele Bartolini <[email protected]>
Add current data size of the server in 'barman status'
2016-01-22 Gabriele Bartolini <[email protected]>
Updated NEWS with current code
2016-01-19 Giulio Calacoci <[email protected]>
Improve archive-wal robustness and log messages
Display clearer error messages when discarding a WAL file.
Also, WAL files that are older than the first backup are
now moved in the 'errors' directory: FAILED backups are now
ignored in this process.
TODO: Add a method to check the presence of files in the error
directory.
Fixes: #24
2016-01-21 Marco Nenciarini <[email protected]>
Move archive-wal code into the wal_archiver module
2016-01-17 Gabriele Bartolini <[email protected]>
Reorder options in barman.5 man page
2016-01-15 Marco Nenciarini <[email protected]>
Add include sorting check in tox flake8 environment
2015-12-05 Giulio Calacoci <[email protected]>
Implement pygzip and pybzip2 compressors
The new pygzip and pybzip2 compressors are implemented using Python's
internal modules for compressing and decompressing gzip and bzip2 files.
This avoids the cost of forking and executing the shell.
Initial idea by Christoph Moench-Tegeder <[email protected]>
2016-01-14 Marco Nenciarini <[email protected]>
Update copyright years to 2016
2016-01-08 Giulio Calacoci <[email protected]>
Add 'receive-wal' cron integration
Add integration of the new command 'receive-wal' during the execution of
the cron command.
If the option 'streaming_archiver' is on, the command 'receive-wal' is
automatically executed as subprocess by the cron command, allowing
Barman to receive WAL files from PostgreSQL using the native streaming
protocol.
TODO: Implement a way to interrupt a running streaming process
2015-12-09 Stefano Zacchiroli <[email protected]>
Add support for the pigz compressor
Pigz on-disk format is the same of gzip, but (de)compression is much
faster due to the usage of CPU parallelism.
For write-intense workloads pigz vs gzip might make the difference,
between struggling to keep up with archiving incoming WALs and being
able to keep up easily.
2016-01-09 Gabriele Bartolini <[email protected]>
Add check() method in WalArchiver classes
Move code from the server.check_postgres() method in
the WalArchiver class, so that each implementation (FileWalArchiver
and StreamingArchiver) perform their specific checks.
Created the RemoteStatusMixin class that implements a cacheable
version of remote status information.
Currently it is only used by the WalArchiver class tree.
TODO: propagate it to all other classes implementing the
get_remote_status() function in a later commit.
2016-01-08 Christoph Moench-Tegeder <[email protected]>
Permit `archive_mode=always` for 9.5 servers
PostgreSQL 9.5 introduces archive_mode=always. Even though Barman's
current framework for checks does not allow yet to correctly monitor
archiving from standby servers, Barman now allows users to set
`archive_mode` to `always`, provided that archiving happens from the master.
2016-01-08 Giulio Calacoci <[email protected]>
Fix server creation and output of check command
Modified the init method of Server Object, managing errors/exception
using the msg_list attribute of the configuration.
Modified the check command output.
2016-01-04 Giulio Calacoci <[email protected]>
Rename get_first_backup and get_last_backup methods
Renamed get_first_backup() and get_last_backup() methods of the
Server and BackupManager classes, respectively into get_first_backup_id()
and get_last_backup_id(), for coherence and code clarity.
Now the fact that the method returns the ID of a backup instead
of a BackupInfo object has been made explicit.
Fix management of backup id during backup deletion
Fix an error that prevents the deletion of an existing
backup while a backup on the same server is in progress.
Fixes #22
2015-12-31 Marco Nenciarini <[email protected]>
Use isort python package to keep imports ordered
2015-12-14 Giulio Calacoci <[email protected]>
Implement `receive-wal` command
The `receive-wal` command receives the stream of transaction logs for a
server. The process relies on `pg_receivexlog` to receive WAL files from
a PostgreSQL server through the streaming protocol.
It is a foreground process which lasts until it receives a SIGINT.
2015-12-31 Marco Nenciarini <[email protected]>
Add support for long running Commands
The Command class now supports the execution of long running
subprocesses, by passing the subprocess output and error streams
to a handler, line by line.
Remove spurious newlines from log lines
Error messages coming from libpq often terminate with a newline.
Always call strip() on strings that have been extracted from
exceptions before logging them.
Make get_remote_status methods behaviour coherent
A 'get_remote_status' method should never raise an exception in case of
error. The expected behaviour is to set missing values to None in the
resulting dictionary.
2015-12-29 Leonardo Cecchi <[email protected]>
Fix exception when streaming connection is unavailable
Previously, when 'streaming_archiver' was on and pg_receivexlog correctly
installed, Barman would raise an AttributeError exception when streaming
connection to PostgreSQL was unavailable, as it could not detect the
server version.
This commit fixes the error by modifying the management of a failed
connection to PostgreSQL through streaming connection. It also adds
an unit test for this scenario, as well as hints for the user during
`barman check` suggesting a possible streaming connection error.
2015-12-28 Leonardo Cecchi <[email protected]>
Propagate "-c" option to any Barman subprocess
The "-c" option lets users specify a custom location for the configuration
file. It must be propagated to every Barman subprocess for consistency
of behaviour.
Fixes #19
2015-12-24 Gabriele Bartolini <[email protected]>
Update documentation about WAL archiving
2015-12-22 Marco Nenciarini <[email protected]>
Manage WAL duplicates in `archive-wal` command
In case a WAL file is archived twice, `archive-wal` will check
if the new file is identical to the already archived one (compressed
WAL files will be decompressed and checked). If yes, the second
file is discarded, otherwise it is saved in the 'errors' directory.
Accept compressed WAL files in incoming directory
In case a WAL file in the incoming directory is already compressed
using a known algorithm, archive it as is.
Add streaming support to 'archive-wal' command
The `archive-wal` command now looks for both archived WAL files
(shipped from PostgreSQL through its `archive_command`) and streamed
ones (via the `receive-wal` command).
2015-12-24 Giulio Calacoci <[email protected]>
Add sleep time option to `barman-wal-restore` script
Introduce the '-s seconds' option to the barman-wal-restore script.
After a failure of the get-wal command, the script will sleep for
the specified amount of seconds (default 0, no wait) before
exiting the restore_command from PostgreSQL.
Closes #7
2015-12-22 Marco Nenciarini <[email protected]>
Add `streaming_wals_directory` and `errors_directory` options
Make sure WAL archiving is atomic. Fixes: #9,#12
2015-12-15 Marco Nenciarini <[email protected]>
Get rid of pytest warnings from pytest-catchlog
2015-12-11 Marco Nenciarini <[email protected]>
Restore compatibility with PostgreSQL 8.3
On PostgreSQL older than 8.4, disable the query that detects those
settings coming from an included file - as the required pg_setting
field was only included in that release.
2015-11-24 Marco Nenciarini <[email protected]>
Fixes possible unhandled exceptions in barman.postgres
Improve the testing coverage of barman.postgres module.
2015-12-06 Christoph Moench-Tegeder <[email protected]>
Remove redundant sete[gu]id() calls
Python's documentation of the os.setuid/os.setgid calls is
oversimplified to the point of being wrong. Under the hood,
the setuid(2)/setgid(2) functions are used, thus making these
calls as POSIX compliant as the underlying operating system.
As barman won't be installed SUID (it's an interpreter file),
effective, real and saved user id should always be the same.
That way, the only reason to use setuid() family calls at all
is for a privileged user (root) to change over to the barman
(unprivileged) user. According to POSIX.1-2013, the setuid()
call changes all three (real, effective and saved) uids if
called by a privileged user (the same holds for setgid() and
the group ids). In this construct, the additional seti[gu]id
calls are redundant no-ops and can be removed.
2015-11-27 Giulio Calacoci <[email protected]>
Add support for 'streaming_archiver' option
Add a global/server boolean option called 'streaming_archiver' which
enables the use of the PostgreSQL's streaming protocol to receive
transaction logs from a server.
If set to 'on', Barman expects to find `pg_receivexlog` in the PATH
(see `path` option) and that streaming connection for the server is
properly working. Subsequently, it activates both proper connection
checks and management of WAL files.
Refactored the code to use a new class, the StreamingWalArchiver,
which is responsible for managing WAL files using a streaming
connection.
Add support for 'archiver' option
Add a global/server boolean option called 'archiver' which
enables continuous WAL archiving (through log shipping using
PostgreSQL's archive_command) for a specific server.
If set the 'true' (default), Barman expects that PostgreSQL
continously deposits WAL files in the 'incoming' directory
of that server, and subsequently activates proper checks and
management.
Refactored the code to use a new class, the FileWalArchiver.
The class is in charge of both archival and compression of WAL files.
This is the first step towards the implementation of streaming
archiving support.
2015-11-25 Marco Nenciarini <[email protected]>
Reorder constants in barman.config module
2015-11-20 Giulio Calacoci <[email protected]>
Add `streaming_conninfo` server option
Added the `streaming_conninfo` option to Barman configuration.
This option (with server scope only), adds the support in Barman
for a streaming replication connection to a PostgreSQL server.
Added also a simple check for the barman check command, that tests
that the streaming connection to PostgreSQL is properly working.
2015-11-13 Giulio Calacoci <[email protected]>
Add support for `path_prefix` configuration option
The `path_prefix` global/server option can contain one
or more absolute paths, separated by colon, where Barman
looks for executable files.
The paths specified in `path_prefix` are tried before the
ones specified in `PATH` environment variable.
2015-11-10 Gabriele Bartolini <[email protected]>
Refactored access to PostgreSQL
Created the 'postgres' module which is responsible for any communication
with a PostgreSQL server, wrapping all connection and query management
activities. This module is the only point of access to PostgreSQL.
2015-11-06 Stefano Bianucci <[email protected]>
Rename `copy_method` configuration key to `backup_method`
2015-11-03 Giuseppe Broccolo <[email protected]>
Create an implicit restore point at the end of a backup
At the end of a backup, if the PostgreSQL version is 9.1 or newer,
create an implicit restore point using the pg_create_restore_point()
function.
2015-11-11 Gabriele Bartolini <[email protected]>
Set version to 1.6.0a1
2015-11-13 Marco Nenciarini <[email protected]>
Update the ChangeLog file
Prepared version 1.5.1
2015-11-13 Giulio Calacoci <[email protected]>
Create pg_xlog/archive_status directory at the end of recovery
On PostgreSQL 8.3, the pg_xlog/archive_status directory is not
automatically created, if missing, during the startup. To avoid errors
Barman now creates that directory at the end of any recovery operation.
2015-11-13 Marco Nenciarini <[email protected]>
Converted sphinx directory README to Markdown
2015-11-10 Marco Nenciarini <[email protected]>
Pin (temporarily) pytest-catchlog to version 1.1
The pytest-catchlog release 1.2.0 broke Python 2.6 compatibility, so pin
the 1.1 version until it will be restored.
Ref: https://github.com/eisensheng/pytest-catchlog/pull/15
In latest release of pytest-catchlog the result of caplog.records() call
is a copy of the event list so any modification of that has no global
effect. Change the code that uses caplog.records() to not rely on the
previous undocumented behaviour.
2015-11-05 Marco Nenciarini <[email protected]>
Fix a typo in barman-wal-restore help output
2015-11-04 Marco Nenciarini <[email protected]>
Update the ChangeLog file
Avoid forcing arcfour cypher in barman-wal-restore
OpenSSH 6.7 dropped many low security algorithms, and arcfour is one of
them. So we stop forcing it in the script, allowing the user to define
the wanted algorithm in ~/.ssh/config
Ref: http://www.openssh.com/txt/release-6.7
2015-11-04 Giulio Calacoci <[email protected]>
Improve error messaging for missing config files
2015-11-04 Gabriele Bartolini <[email protected]>
Set version to 1.5.1b1
2015-10-27 Giulio Calacoci <[email protected]>
Manage 'wal_level' only for PostgreSQL >= 9.0
Really fixes #3
2015-10-26 Marco Nenciarini <[email protected]>
Fix all E731 pep8 errors
Always use a def statement instead of an assignment statement that binds
a lambda expression directly to a name.
See: https://www.python.org/dev/peps/pep-0008/#programming-recommendations
2015-10-22 Marco Nenciarini <[email protected]>
Update the ChangeLog file
2015-10-22 Gabriele Bartolini <[email protected]>
NEWS for 1.5.1a1
Set version to 1.5.1a1
Revert version to 1.5 branch due to relevant bug fixing
2015-10-12 Giulio Calacoci <[email protected]>
Add the 'archive-wal' command
The 'archive-wal' command executes the WAL maintenance operations on a
given server.
This command is automatically executed as a subprocess by the cron
command, allowing the parallel execution of WAL archiving on
different servers.
2015-10-20 Giuseppe Broccolo <[email protected]>
Avoid 'wal_level' check on PostgreSQL version < 9.0
Conditionally skip 'wal_level' check in PostgreSQL
versions prior to 9.0.
Fixes #3
Avoid retention policy checks during the recovery
Additionally, skip any missing tablespace directory during the deletion
of a backup (like we already do with missing pgdata directory)
2015-10-20 Marco Nenciarini <[email protected]>
Fix more incorrect mock assert calls in unit tests
Add flake8-mock plugin in flake8 tox environment to make sure it will
not happen again.
Some more cleanup of testing infrastructure has been done:
* Switch from pytest-capturelog (unresponsive upstream) to
pytest-catchlog.
* Remove the version pinning from mock as 1.3.0 supports py2.6 again.
* Add flake8-copyright and flake8-string-format plugins.
2015-10-09 Giulio Calacoci <[email protected]>
Allow parallel cron execution for different servers
Allow the execution of multiple 'barman cron' processes, each one
handling a different server. Servers will be handled sequentially,
skipping those that are already being served by another cron process.
2015-10-22 Marco Nenciarini <[email protected]>
Fix calculation of backup size
In Barman 1.5.0 the internal directory structure of a backup has been
changed, moving tablespaces from being inside the data directory to
being inside the backup directory. The method backup_fsync_and_set_sizes()
now takes that into account by running against the whole backup directory.
Fixes #5
2015-10-12 Marco Nenciarini <[email protected]>
Fix some incorrect mock assert calls in unit tests
2015-10-06 Giulio Calacoci <[email protected]>
Support for mixed compression types in WAL files (#61)
Decompress each WAL file using the specific algorithm
reported in the XLOG archive (xlogdb).
Improve management of xlog.db errors
Better management of errors during the decoding of the name
of an xlog segment. Added a hint that suggests to run
"barman rebuild-xlogdb" to fix corruptions in the xlogdb file.
2015-10-02 Gabriele Bartolini <[email protected]>
Started version 1.6.0a1
2015-09-25 Marco Nenciarini <[email protected]>
Update the ChangeLog file
Update Copyright notice
2015-09-25 Gabriele Bartolini <[email protected]>
Remove obsolete section from tutorial
Removed a section in the tutorial regarding the 'delete'
command, as pointed out by Ian Barwick.
2015-09-25 Marco Nenciarini <[email protected]>
Enable flake8 in every tox run
2015-09-24 Gabriele Bartolini <[email protected]>
Prepared version 1.5.0 for final release
2015-09-24 Marco Nenciarini <[email protected]>
Update tox.ini to allow specifying a target test
Also add .cache directory, which is created by latest tox, to .gitignore
2015-09-24 Giulio Calacoci <[email protected]>
Changed import of call() method.
Now is compatible with all versions of py.test libraries
2015-09-16 Giulio Calacoci <[email protected]>
Support for non-critical checks during backup
Add a filter for non-critical checks during backup operations.
This patch fixes a bug that prevented users from taking a new
backup when minimum redundancy or smelly backup checks failed.
2015-09-15 Marco Nenciarini <[email protected]>
Update the ChangeLog file
2015-09-15 Gabriele Bartolini <[email protected]>
Prepared for 1.5.0 alpha 1
2015-09-09 Gabriele Bartolini <[email protected]>
Converted man pages to Markdown
2015-09-08 Gianni Ciolli <[email protected]>
Some small fixes to the tutorial
2015-09-01 Francesco Canovai <[email protected]>
Updated spec file for RPM building
2015-09-04 Giuseppe Broccolo <[email protected]>
Add barman-wal-restore script
Add a simple bash script to be used as `restore_command`
in a standby scenario, as fallback method. The script
uses ssh to connect to the Barman server and requests
the required WAL file for recovery.
The script checks that destination path is not a directory.
2015-08-27 Gabriele Bartolini <[email protected]>
Convert tutorial to Markdown
2015-08-28 Giulio Calacoci <[email protected]>
Manage options without '=' in PostgreSQL configuration files
2015-08-18 Gabriele Bartolini <[email protected]>
Allow 'pre' retry hook scripts to stop the command
Add EXIT_ABORT_STOP (63) and EXIT_ABORT_CONTINUE (62) exit codes
to control how a retry hook script is aborted.
Termination of a retry hook script with EXIT_ABORT_CONTINUE informs
Barman to continue with its operations.
By terminating a retry hook script with EXIT_ABORT_STOP, users
request Barman to stop its main operation (i.e. backup or WAL archival).
EXIT_ABORT_CONTINUE is implemented by every retry hook script.
EXIT_ABORT_STOP is currently implemented only with 'pre_backup_retry_script'
and 'pre_archive_retry_script'.
EXIT_ABORT_STOP is currently ignored by 'post_backup_retry_script' and
'post_archive_retry_script', and its behaviour in these cases is
identical to EXIT_ABORT_CONTINUE.
2015-08-21 Marco Nenciarini <[email protected]>
Add flake8 tox environment
2015-08-18 Gabriele Bartolini <[email protected]>
Documentation for 'barman_lock_directory'
2015-08-18 Giulio Calacoci <[email protected]>
Analyse include directives for PostgreSQL
Check if PostgreSQL administrators take advantage of include
directives and specify additional files. Include directives
(include, include_if_exists, include_dir) are not supported
in Barman for files that reside outside PGDATA.
During backup, warn users and list the files that require
manual backup. During recovery, warn users about the presence
of include directives in PostgreSQL configuration.
2015-08-18 Gabriele Bartolini <[email protected]>
Workaround for rsync on SUSE Linux
Many thanks to Christoph Moench-Tegeder <[email protected]>
for his workaround proposal. This fixes the outstanding issue
on SUSE Linux - previously raised by issues #13 and #26.
See also: https://bugzilla.opensuse.org/show_bug.cgi?id=898513
2015-08-17 Gabriele Bartolini <[email protected]>
Added copy_method option (fixed to rsync)
2015-08-06 Giulio Calacoci <[email protected]>
Support for 'retry' hook scripts for backup and WAL archiving
A 'retry' hook script is a special kind of hook scripts that Barman
tries to run indefinitely until it either returns a SUCCESS (0) or
an ABORT (63) exit code.
Safe hook scripts are executed immediately before (pre) and after (post)
the command execution. Standard hook scripts are executed immediately
before (pre) and after (post) the retry hook scripts.
This patch adds support for pre/post retry hook scripts for backup
and WAL archiving.
The following four global/server configuration options have been added:
* pre_backup_retry_script: executed before a backup
* post_backup_retry_script: executed after a backup
* pre_archive_retry_script: executed before a WAL archive operation
* post_archive_retry_script: executed after a WAL archive operation
By default, no retry hook script is executed. Environment variables
are identical to the equivalent standard hook script.
2015-08-12 Gabriele Bartolini <[email protected]>
Updated AUTHORS file
2014-05-29 Giulio Calacoci <[email protected]>
Support for the 'get-wal' command
The 'barman get-wal' command allows users to fetch any WAL file
from the archive of a specific server in Barman.
2015-08-21 Marco Nenciarini <[email protected]>
Add simple Travis CI integration
2015-08-11 Gabriele Bartolini <[email protected]>
Set version 1.5.0a1
2015-07-30 Giulio Calacoci <[email protected]>
Preserve Timeline history files. Fixes #70.
Added check for the management of history files during the removal of a
backup or during normal maintenance operations (cron).
2015-08-06 Giulio Calacoci <[email protected]>
Forbid the delete of a running backup
Block the execution of a barman delete command on a backup that is in progress.
Use locks to ensure that there are no running backups on that server.
Otherwise check for the position of the backup to be deleted in the
catalogue and its status: if it is the first backup and its status is STARTED or EMPTY,
the backup is running and delete is forbidden.
2015-08-03 Giulio Calacoci <[email protected]>
Follow symlinks when checking directory paths
Check conflicting paths in configuration files using canonical paths and
following symlinks when necessary.
2015-07-13 Francesco Canovai <[email protected]>
Pin mock==1.0.1 for testing.
In version 1.1.x mock has changed some behaviours and is currently
incompatible with our unit tests.
2015-07-08 Stefano Bianucci <[email protected]>
Execute check() before starting a backup
Execute the full suite of tests from barman check command before
starting a backup. Skip the execution of a backup in case check
fails.
Add a strategy for managing the results of the checks. Now every
check is properly logged as error (failure) or debug (success).
2015-07-03 Giulio Calacoci <[email protected]>
Support code documentation using Sphinx
Generate code documentation using Sphinx autodocs
2015-07-13 Giulio Calacoci <[email protected]>
Modified test for correct management of timezone
2015-07-10 Marco Nenciarini <[email protected]>
Properly support BackupInfo serialization in JSON format.
2015-07-01 Giulio Calacoci <[email protected]>
Improved management of configuration in tests
Improved and simplified the management of configurations in tests. Added
a method for the creation of dictionaries containing all the keys that
are usually present in a configuration. Updated tests accordingly.
2015-06-18 Giulio Calacoci <[email protected]>
Second part of the backup_executor module's refactor
Refactored and streamlined the executor module. Introduced a specific
class for physical backup with Rsync through Ssh, as well as a strategy
pattern for the management of exclusive and concurrent backups (for
backups from a standby).
2015-06-23 Gabriele Bartolini <[email protected]>
Standard error management for server commands
Standardised the process of managing errors with server commands in
barman/cli.py. By default, inactive servers are skipped (without error)
as well as temporarily disabled servers (with error). No distinction is
made between calling a command with one server as target or with a list
of them (including 'all'). Exceptions are check (no server is skipped,
errors are returned only for active servers), cron (no error is ever
returned), list-server and diagnose (both managing active/disabled
servers with no errors). Inactive servers are the ones with 'active'
option set to False. Disabled servers are the ones with internal
directory conflicts (e.g. WALs directory = base backup directory).
2015-06-23 Gabriele Bartolini <[email protected]>
Asciidoc support for man pages and tutorial
2015-06-16 Giulio Calacoci <[email protected]>
Fixed error in WAL rate calculation.
Solved an error during the evaluation of the WAL rate for a backup.
Added two basic unit tests.
2015-06-12 Stefano Bianucci <[email protected]>
Add check for wal_level
For better usability, warn users about setting a proper value
for wal_level setting in PostgreSQL.
2015-05-14 Stefano Bianucci <[email protected]>
Add check for conflicting paths in Barman's configuration
Added controls for path-clash during the creation of Barman servers.
If there are conflicting paths, Barman will disable those servers
containing errors.
If a potentially destructive command like "backup" is issued on a server
containing conflicts, Barman exits with an error message.
2015-05-21 Giulio Calacoci <[email protected]>
Complete refactor of the 'recover' command
The main 'recover' command has been completely refactored, through
the creation of a separate module, called 'recovery_executor'.
The RecoveryExecutor class now embodies both local and remote
operations, laying the road for future improvements.
This patch also fixes #68, by disabling dangerous settings in
postgresql.auto.conf (available from PostgreSQL 9.4).
Basic unit tests have been added.
2015-05-19 Giulio Calacoci <[email protected]>
Rename class Server to ServerConfig in barman.config module
Previously both barman.config and barman.server modules had a Server
class. The former has now been renamed to ServerConfig, hence removing
the ambiguity.
2015-05-21 Marco Nenciarini <[email protected]>
Fix incompatibility with tox version >= 2
2015-05-08 Giulio Calacoci <[email protected]>
Make sure that even an EMPTY backup has a server set.
2015-05-07 Giulio Calacoci <[email protected]>
Improve xlog.db integrity (Closes: #67)
* Execute flush() and fsync() after writing a line in xlog.db
* Execute fsync() on incoming directory after every WAL is archived
2015-04-13 Giulio Calacoci <[email protected]>
Remove unused 'server' argument from WalFile.from_xlogdb_line()
This also fix regression in 'barman delete' command introduced with
commit 7ac8fe9c41fd7e5636f370abdc92ca785057263e.
2015-04-13 Giulio Calacoci <[email protected]>
Fix exception during error handling in barman recovery (Closes: #65)
2015-03-24 Giulio Calacoci <[email protected]>
Improved cache management of backups
Streamlined the management of the cache of the backups.
It is now possible to register and remove a backup from the cache.
The cache structure has been simplified and now it is a simple
dictionary of backups. Status filters are applied by the
get_available_backups() method.
Managed registration and removal of a backup in the cache
during backup operations.
2015-03-02 Giulio Calacoci <[email protected]>
Create backup_executor module and refactor backup.
Extract all the methods relative to the execution of a backup into a
dedicated object.
The RsyncBackupExecutor encapsulates the operation of backing up a
remote server using rsync and ssh to copy files.
2015-03-27 Marco Nenciarini <[email protected]>
Improved management of xlogb file
The xlogdb file is now correctly fsynced when updated.
Also, the rebuild-xlogdb command now operates on a temporary