On Wednesday September 22 2004 9:14, Jan Wieck wrote:
> On 9/22/2004 6:10 PM, Christopher Browne wrote:
> > "Ed L." <pgsql at bluepolka.net> writes:
> >> I see that sl_log_1 "stores each change to be propagated to
> >> subscriber nodes."  Can anyone explain the purpose of sl_log_1
> >> vs. sl_log_2?  Looking at the source, it appears the same data is
> >> inserted into both.
> >
> > Eventually the plan is for the triggers to insert data into either or
> > the other, which means that we're "free" do maintenance on the table
> > not presently in use.
>
> The logswitch and vacuum full or truncate will be done on a daily or
> weekly base, or even on operator request only. This will take care of a
> logtable bloat due to prolonged downtime of a subscriber.

How do you trigger a switch between sl_log_1 and sl_log_2?  Is this 
functionality implemented?

Ed