Re: Odd behaviour with WAL and pg_stop_backup

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



"Donald Fraser" <postgres@xxxxxxxxxxxxxxx> writes:
> We have been testing the on-line backup of PostgreSQL and after issuing a 
> pg_stop_backup() PostgreSQL is still using the archive command, as set in 
> postgresql.conf, for every new WAL block generated.

Um ... why would that surprise you?  That facility is designed for
continuous archiving of WAL.  If you want to make a one-shot dump,
pg_dump is a much better tool.

			regards, tom lane


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux