Robert Treat wrote: > On Wednesday 01 October 2008 10:27:52 Tom Lane wrote:
> > Your optimism is showing ;-). XLogInsert routinely shows up as a major > > CPU hog in any update-intensive test, and AFAICT that's mostly from the > > CRC calculation for WAL records. > > Yeah... for those who run on filesystems that do checksumming for you, I'd > bet > they'd much rather see time spent in turning that off rather than > checksumming everything else. (just guessing) I don't think it can be turned off, because ISTR a failed checksum is used to detect end of the WAL stream to be recovered. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
