On Wed, Apr 21, 2010 at 2:04 PM, Jan Wieck <JanWieck at yahoo.com> wrote:
> On 4/21/2010 2:38 PM, Scott Marlowe wrote:
>>
>> So, I had a query that blocked all updates going out of the sl_log_2
>> table, and it's 13Gig.  sl_log_1 is empty.
>>
>> IS the logswitch_finish() command an acceptable method for forcing the
>> replication engine to switch from 2 to 1 so I can vacuum full 2?
>
> It is completely safe to call logswitch_finish() at any time. It may or may
> not actually do something.
>
> In your case, I presume the value of sl_log_status is 2. This means it is
> waiting for sl_log_2 to become empty and once that happens, it will truncate
> it and set sl_log_status to 0.

So, if I let the system just sit quiescent for a while, it should
straighten things out?