Re: AW: Backup, restore & pg_dump
От | Vadim Mikheev |
---|---|
Тема | Re: AW: Backup, restore & pg_dump |
Дата | |
Msg-id | 014b01c03a07$8c4fdc80$bb7a30d0@sectorbase.com обсуждение исходный текст |
Ответ на | AW: AW: Backup, restore & pg_dump (Zeugswetter Andreas SB <ZeugswetterA@wien.spardat.at>) |
Список | pgsql-hackers |
> Yes, writes are only necessary when "too many dirty pages" > are in the buffer pool. Those writes can be done by a page flusher > on demand or during checkpoint (don't know if we need checkpoint, > but you referred to doing checkpoints). How else to know from where in log to start redo and how far go back for undo ? > > Currently records inserted by aborted transactions remain in db > > untill vacuum. I try to rollback changes - ie *delete* inserted > > tuples on abort (though could do not do this), - isn't there > > some difference now? > > this has two sides: less space wastage, but slower rollback. > What you state is a separate issue, and is not part of the > startup rollforward for committed tx'ns. It is part of the rollback > of aborted tx'ns. And I've stated this as separate feature. Vadim
В списке pgsql-hackers по дате отправления: