On Sat, Jan 11, 2014 at 11:26 PM, François Beausoleil <franc...@teksol.info>wrote:
> Hi all, > > I'm using OmniPITR to build a new slave. According to pg_stat_activity, > pg_stop_backup has been running for nearly 11 hours. The WAL archive > command is running just fine and reporting "Segment X successfully sent to > all destinations". > > I had the same issue almost a year ago ( > http://www.postgresql.org/message-id/9cc57302-10f8-4678-bbd3-028ec6b57...@teksol.info), > but don't have permission issues this time around. > > What could cause a pg_stop_backup() to run for such a long time? > Can't speak for the OmniPITR specific parts, but typically the archive_command reacting strangely would cause pg_stop_backup() to wait. You include the logs from omniptr, but do you get anything in the *postgresql* logs? If it's the archive command it should clearly tell you that. It should also tell you if you can safely cancel the pg_stop_backup() command. -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/
