Jan Wieck <JanWieck at Yahoo.com> writes:

> On 11/13/2004 11:08 AM, cbbrowne at ca.afilias.info wrote:
>
>>> On 11/12/2004 1:17 PM, CVS User Account wrote:
>>>
>>>> Log Message:
>>>> -----------
>>>> Add FUNCTION generate_sync_event () - to try to add SYNCs even if slon
>>>> isn't running
>>>
>>> But what calls this function? We can't unload that burden to the
>>> application.
>> My first thought had been to get the logtrigger() function to
>> occasionally
>> run it.  That would be liable to be a hefty burden, unfortunately.
>> Rod Taylor's thought of running it in a cron job seems pretty
>> appropriate;
>> having the granularity of once a minute ought to be enough to at least
>> avoid the REALLY big syncs that result from the origin's slon being down
>> for a while.
>
> On a second thought, that alone is still far from optimal. Remember
> that we are leaning towards sync grouping more and more, so even once
> a minute ... with the default -g20 this means 20 minute
> chunks. Sure. better than what we have right now anyway. There should
> be a trivial script and README added to the tools directory, easy to
> add to postgres' crontab.

I have made a couple further changes:

 - Pass the function an interval; it now doesn't bother doing anything
   if there has been a sync in the past (INTERVAL).  That way, if all
   is going well, this doesn't have to do any work.

 - Wrote a trivial shell script containing docs in the "tools"
   directory.

 - Added documentation to the Wiki, which will, soon enough, flow into
   the documentation tree...

Thanks for the suggestions, Rod and Jan!
-- 
"cbbrowne","@","ca.afilias.info"
<http://dev6.int.libertyrms.com/>
Christopher Browne
(416) 673-4124 (land)