Re: NOLOGGING option, or ?
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Jochem van Dieten <jochemd@gmail.com>, pgsql-hackers@postgresql.org
Date: 2005-06-01T15:43:24Z
Lists: pgsql-hackers
Bruce Momjian <pgman@candle.pha.pa.us> writes: > Jochem van Dieten wrote: >> Why only on an empty table? What is the problem with bypassing WAL on >> any table as long as all files of that table are fsync'ed before >> commit? > Because adding rows to a table might modify existing pages, and if the > COPY fails, you have to restore those pages to a consistent state, and > make sure they are recovered for partial page writes, which we can't do > without WAL. With an initially empty table, you can just throw away the > file system file. You have also got to think about the effects on the table's indexes ... regards, tom lane