mirror of
https://github.com/pgbackrest/pgbackrest.git
synced 2024-12-14 10:13:05 +02:00
Tracking down a lockup in the restore threads. It doesn't happen in backup - they are the same except that restore uses the ThreadGroup object. I'm beginning to think that threads and objects don't play together very nicely. Objects in threads seems OK, but threads in objects, not so much.
This commit is contained in:
parent
7bee43372d
commit
d2602a5c07
@ -1190,6 +1190,8 @@ sub backup_file_thread
|
||||
{
|
||||
&log(INFO, $strLog);
|
||||
}
|
||||
|
||||
&log(TRACE, "thread waiting for new file from queue");
|
||||
}
|
||||
|
||||
&log(DEBUG, "thread ${iThreadIdx} exiting");
|
||||
|
@ -724,6 +724,8 @@ sub restore_thread
|
||||
{
|
||||
$iQueueIdx = 0;
|
||||
}
|
||||
|
||||
&log(TRACE, "thread waiting for new file from queue: queue ${iQueueIdx}, start queue ${iQueueStartIdx}");
|
||||
}
|
||||
while ($iQueueIdx != $iQueueStartIdx);
|
||||
|
||||
|
@ -55,7 +55,7 @@ sub BackRestTestBackup_PgConnect
|
||||
}
|
||||
|
||||
####################################################################################################################################
|
||||
# BackRestTestBackup_Disconnect
|
||||
# BackRestTestBackup_PgDisconnect
|
||||
####################################################################################################################################
|
||||
sub BackRestTestBackup_PgDisconnect
|
||||
{
|
||||
@ -194,7 +194,7 @@ sub BackRestTestBackup_ClusterStop
|
||||
# Disconnect user session
|
||||
BackRestTestBackup_PgDisconnect();
|
||||
|
||||
# If postmaster process is running them stop the cluster
|
||||
# If postmaster process is running then stop the cluster
|
||||
if (-e $strPath . '/postmaster.pid')
|
||||
{
|
||||
BackRestTestCommon_Execute(BackRestTestCommon_PgSqlBinPathGet() . "/pg_ctl stop -D ${strPath} -w -s -m " .
|
||||
|
Loading…
Reference in New Issue
Block a user