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.


Jan

-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck at Yahoo.com #