| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com> |
| Cc: | Gregory Stark <stark(at)enterprisedb(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Subject: | Re: COMMIT NOWAIT Performance Option |
| Date: | 2007-02-28 19:48:45 |
| Message-ID: | 200702281948.l1SJmjG26774@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jonah H. Harris wrote:
> On 2/28/07, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> > We have several methods suggested to check the blocks, like CRC. My
> > point was that, whatever check method we use, we should be prepared to
> > check on startup, or at least make it the default for a crash restart.
>
> Sounds like it should be a guc. I most certainly wouldn't check the
> entire database, especially if it was over a gigabyte.
Keep in mind if you don't check it on startup, you will be checking it
for every read, which for rare crashes, might not be wise.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonah H. Harris | 2007-02-28 19:52:11 | Re: COMMIT NOWAIT Performance Option |
| Previous Message | Jeff Davis | 2007-02-28 19:48:10 | Re: COMMIT NOWAIT Performance Option |