Quando utilizo slon_watchdog, and I use "ps xa" I look:
7869 pts/0 S 0:00 /usr/bin/perl /usr/bin/slon_watchdog 2 255
9266 pts/0 S 0:01 /usr/bin/slon -p /var/run/slony1/node2.pid -s
1000 -d2 teste
10050 pts/0 Z 0:00 [slon] <defunct>
14351 pts/0 S 0:01 /usr/bin/slon -p /var/run/slony1/node2.pid -s
1000 -d2 teste
15167 pts/0 Z 0:00 [slon] <defunct>
15653 pts/0 S 0:00 /usr/bin/slon -p /var/run/slony1/node2.pid -s
1000 -d2 teste
15989 pts/0 Z 0:00 [slon] <defunct>
16182 pts/0 S 0:00 /usr/bin/slon -p /var/run/slony1/node2.pid -s
1000 -d2 teste
16376 pts/0 Z 0:00 [slon] <defunct>
.
.
.
.
The slon_watchdog create a lot of process, is there a problem with this?
How slon_watchdog don´t create a lot of process?
I start slon_watchdog with:
/usr/bin/perl /usr/bin/slon_watchdog 2 255
I think this my server could have problem with crash.
I use this slon_tools.conf:
if ($ENV{"SLONYNODES"}) {
require $ENV{"SLONYNODES"};
} else {
$CLUSTER_NAME = 'test';
$LOGDIR = '/var/log/slony1';
$SYNC_CHECK_INTERVAL = 1000;
$MASTERNODE = 1;
}
$SLONY_SETS = {
"set1" => {
"set_id" => 1,
"origin" => 2,
"table_id" => 1,
"sequence_id" => 1,
"pkeyedtables" => [
'TABLE1',
'table2',
],
"keyedtables" => {
'table3' => 'index_on_table3',
'table4' => 'index_on_table4',
},
"serialtables" => ["table5"],
"sequences" => ['sequence1',
'sequence2',
],
},
"set2" => {
"set_id" => 2,
"table_id" => 6,
"sequence_id" => 3,
"pkeyedtables" => ["table6"],
"keyedtables" => {},
"serialtables" => [],
"sequences" => [],
},
};
if ($ENV{"SLONYSET"}) {
require $ENV{"SLONYSET"};
}
1;
_______________________________________________
Slony1-general mailing list
[email protected]
http://gborg.postgresql.org/mailman/listinfo/slony1-general
