> > 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, such records shouldn't make the WAL grow much faster.
All redo records have to be at the tuple level, so what higher-level are you talking
about ? (statement level redo records would not be able to reproduce the same
resulting table data (keyword: transaction isolation level))
> The page images are not needed and can be thrown away once the page is
> completely sync'ed to disk or a checkpoint happens.
Actually they should at least be kept another few seconds to allow "stupid"
disks to actually write the pages :-) But see previous mail, they can also
help with various BAR restore solutions.
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2001-07-05 13:47:03|
|Subject: Re: stuck spin lock with many concurrent users |
|Previous:||From: Zeugswetter Andreas SB||Date: 2001-07-05 09:42:37|
|Subject: AW: Re: Backup and Recovery|