From: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
---|---|
To: | "'Vadim Mikheev'" <vmikheev(at)sectorbase(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | AW: AW: Backup, restore & pg_dump |
Date: | 2000-10-20 08:52:22 |
Message-ID: | 11C1E6749A55D411A9670001FA6879633680BD@sdexcsrv1.f000.d0188.sd.spardat.at |
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 ?
I don't know, but if your checkpoint algorithm does not need to block
other activity, that would be great.
The usual way would involve:
writing all dirty pages to disk during checkpoint
block all modifying activity
One other thing I would like to ask, is O_SYNC not available on all platforms ?
Then you could avoid the (or some) fsync calls in xlog.c ?
And is there a possibility to add -F mode without fsyncs to xlog.c ?
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Continuing Technical Education | 2000-10-20 12:16:55 | Re: Conditional query plans. |
Previous Message | Chris | 2000-10-20 07:35:41 | Re: INHERITS doesn't offer enough functionality |