> > Also, isn't the WAL format rather bulky to archive hours and hours of?
If it were actually too bulky, then it needs to be made less so, since that
directly affects overall performance :-)
> > I would expect high-level transaction redo records to be much more compact;
> > mixed into the WAL
> > > > I imagine a daemon extracting redo log entries from WAL segments,
> > > > asynchronously. Mixing redo log entries into the WAL allows the WAL
> > > > to be the only synchronous disk writer in the system, a Good Thing.
> > >
> > > This comes up periodically now. WAL currently already h
> I imagine a daemon extracting redo log entries from WAL segments,
> asynchronously. Mixing redo log entries into the WAL allows the WAL
> to be the only synchronous disk writer in the system, a Good Thing.
This comes up periodically now. WAL currently already has all the info
that would be
