Greg Stark wrote: > Bruce Momjian <pgman@candle.pha.pa.us> writes: > > > I see your point. New text is: > > > > 4 Again connect to the database as a superuser, and issue the command > > > > SELECT pg_stop_backup(); > > > > This should return successfully. > > > > 5 Once the WAL segment files used during the backup are archived as > > part of normal database activity, you are done. > > > > > sure that they get a good base backup. It actually seems like something > > > that maybe pg_stop_backup() should do in the future. > > > > Yes, I added that to the TODO list: > > > > * Force archiving of partially-full WAL files when pg_stop_backup() is > > called or the server is stopped > > You could even make pg_stop_backup() hang until that's complete.
You mean don't force the archive copy but just have pg_stop_backup() hang until the files fill? Yea, we could do that, but there is no way to know how long the hang might take. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
