Re: Updating FSM on recovery

Simon Riggs <simon@2ndQuadrant.com> writes:
> Or possibly an XLogInsertDeferred() which just queues up some work so
> the next time we call XLogInsert() it will insert the deferred work as
> well as the main work all in one lock cycle. It would only be usable for
> low priority info like FSM stuff that isn't needed for recovery. Maybe
> we could do that with hints also.

If it isn't needed for recovery, why would we be logging it at all?
        regards, tom lane