From: | "Vadim Mikheev" <vmikheev(at)sectorbase(dot)com> |
---|---|
To: | "Zeugswetter Andreas SB" <ZeugswetterA(at)wien(dot)spardat(dot)at> |
Cc: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: AW: Backup, restore & pg_dump |
Date: | 2000-10-19 20:02:45 |
Message-ID: | 014b01c03a07$8c4fdc80$bb7a30d0@sectorbase.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2000-10-19 20:30:17 | Re: make depend (Re: Coming attractions: VPATH build; make variables issue) |
Previous Message | Vadim Mikheev | 2000-10-19 19:57:34 | Re: SetQuerySnapshot() for utility statements |