Bruce Momjian <[EMAIL PROTECTED]> writes:
> The only problem is that we would no longer have control over which
> pages made it to disk. The OS would perhaps write pages as we modified
> them. Not sure how important that is.
Unfortunately, this alone is a *fatal* objection. See nearby
discussions about WAL behavior: we must be able to control the relative
timing of WAL write/flush and data page writes.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
- [HACKERS] CeBit Michael Meskes
- [HACKERS] WAL & SHM principles Martin Devera
- Re: [HACKERS] WAL & SHM principles Bruce Momjian
- Re: [HACKERS] WAL & SHM principles Martin Devera
- Re: [HACKERS] WAL & SHM principles Tom Lane
- Re: [HACKERS] WAL & SHM principles Bruce Momjian
- Re: [HACKERS] WAL & SHM princip... Martin Devera
- Re: [HACKERS] WAL & SHM pri... Tim Allen
- Re: [HACKERS] WAL & SHM pri... Bruce Momjian
- Re: [HACKERS] WAL & SHM... Martin Devera
- Re: [HACKERS] WAL & SHM... Giles Lean
- Re: [HACKERS] WAL & SHM... Ken Hirsch
- Re: [HACKERS] WAL & SHM... Ken Hirsch
- Re: [HACKERS] WAL & SHM... Matthew Kirkwood
- Re: [HACKERS] WAL & SHM... Alfred Perlstein
