--- a/clustertest/conf/slon.1.conf.sample +++ b/clustertest/conf/slon.1.conf.sample @@ -91,7 +91,7 @@ cluster_name='disorder_replica' # maximum time planned for grouped SYNCs # If replication is behind, slon will try to increase numbers of -# syncs done targetting that they should take this quantity of +# syncs done targeting that they should take this quantity of # time to process. in ms # Range [10000,600000], default 60000. desired_sync_time=6000 --- a/clustertest/conf/slon.2.conf.sample +++ b/clustertest/conf/slon.2.conf.sample @@ -91,7 +91,7 @@ cluster_name='disorder_replica' # maximum time planned for grouped SYNCs # If replication is behind, slon will try to increase numbers of -# syncs done targetting that they should take this quantity of +# syncs done targeting that they should take this quantity of # time to process. in ms # Range [10000,600000], default 60000. desired_sync_time=6000 --- a/clustertest/conf/slon.3.conf.sample +++ b/clustertest/conf/slon.3.conf.sample @@ -91,7 +91,7 @@ cluster_name='disorder_replica' # maximum time planned for grouped SYNCs # If replication is behind, slon will try to increase numbers of -# syncs done targetting that they should take this quantity of +# syncs done targeting that they should take this quantity of # time to process. in ms # Range [10000,600000], default 60000. desired_sync_time=6000 --- a/clustertest/conf/slon.4.conf.sample +++ b/clustertest/conf/slon.4.conf.sample @@ -91,7 +91,7 @@ cluster_name='disorder_replica' # maximum time planned for grouped SYNCs # If replication is behind, slon will try to increase numbers of -# syncs done targetting that they should take this quantity of +# syncs done targeting that they should take this quantity of # time to process. in ms # Range [10000,600000], default 60000. desired_sync_time=6000 --- a/clustertest/conf/slon.5.conf.sample +++ b/clustertest/conf/slon.5.conf.sample @@ -91,7 +91,7 @@ cluster_name='disorder_replica' # maximum time planned for grouped SYNCs # If replication is behind, slon will try to increase numbers of -# syncs done targetting that they should take this quantity of +# syncs done targeting that they should take this quantity of # time to process. in ms # Range [10000,600000], default 60000. desired_sync_time=6000 --- a/doc/adminguide/slon.sgml +++ b/doc/adminguide/slon.sgml @@ -240,7 +240,7 @@ If replication is running behind, slon will gradually increase the numbers of SYNCs grouped - together, targetting that (based on the time taken for the + together, targeting that (based on the time taken for the last group of SYNCs) they shouldn't take more than the specified desired_sync_time value. --- a/doc/adminguide/slonconf.sgml +++ b/doc/adminguide/slonconf.sgml @@ -523,7 +523,7 @@ Maximum time planned for grouped SYNCs. If replication is behind, slon will try to increase numbers - of syncs done targetting that they should take this quantity + of syncs done targeting that they should take this quantity of time to process. This is in Range [10000,600000] ms, default 60000. --- a/doc/adminguide/slonik_ref.sgml +++ b/doc/adminguide/slonik_ref.sgml @@ -2853,7 +2853,7 @@ EXECUTE SCRIPT ( Before &slony1; version 1.2, the entire DDL script was submitted as one PQexec() request, with the implication that the entire script was parsed - based on the state of the database before invokation of the + based on the state of the database before invocation of the script. This means statements later in the script cannot depend on DDL changes made by earlier statements in the same script. Thus, you cannot add a column to a table and add constraints to --- a/doc/adminguide/testbed.sgml +++ b/doc/adminguide/testbed.sgml @@ -11,7 +11,7 @@ distribution, and induced load via runni pgbench. Unfortunately, the tests required human intervention to control -invokation and shutdown of tests, so running them could not be readily +invocation and shutdown of tests, so running them could not be readily automated. Test bed framework --- a/share/slon.conf-sample +++ b/share/slon.conf-sample @@ -93,7 +93,7 @@ # maximum time planned for grouped SYNCs # If replication is behind, slon will try to increase numbers of -# syncs done targetting that they should take this quantity of +# syncs done targeting that they should take this quantity of # time to process. in ms # Range [10000,600000], default 60000. #desired_sync_time=60000 --- a/src/slon/confoptions.c +++ b/src/slon/confoptions.c @@ -94,7 +94,7 @@ static struct config_int ConfigureNamesI (const char *) "desired_sync_time", gettext_noop("maximum time planned for grouped SYNCs"), gettext_noop("If replication is behind, slon will try to increase numbers of " - "syncs done targetting that they should take this quantity of " + "syncs done targeting that they should take this quantity of " "time to process"), SLON_C_INT }, --- a/tools/mkservice/slon-mkservice.sh +++ b/tools/mkservice/slon-mkservice.sh @@ -280,7 +280,7 @@ log_timestamp 0 # multilog will inse #vac_frequency 3 # Maximum time planned for grouped SYNCs. If replication is behind, slon will -# try to increase numbers of syncs done targetting that they should take this +# try to increase numbers of syncs done targeting that they should take this # quantity of time to process. If the value is set to 0, this logic will be # ignored. # Range [10000,600000] ms, default 60000. --- a/tools/mkslonconf.sh +++ b/tools/mkslonconf.sh @@ -115,7 +115,7 @@ conn_info='${dsn}' # maximum time planned for grouped SYNCs # If replication is behind, slon will try to increase numbers of -# syncs done targetting that they should take this quantity of +# syncs done targeting that they should take this quantity of # time to process. in ms # Range [10000,600000], default 60000. desired_sync_time=60000