Re: COMMIT NOWAIT Performance Option

From: "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>
To: "Bruce Momjian" <bruce(at)momjian(dot)us>
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:41:42
Message-ID: 36e682920702281141y229ed97fx84a25a22f9a03928@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

--
Jonah H. Harris, Software Architect | phone: 732.331.1324
EnterpriseDB Corporation | fax: 732.331.1301
33 Wood Ave S, 3rd Floor | jharris(at)enterprisedb(dot)com
Iselin, New Jersey 08830 | http://www.enterprisedb.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2007-02-28 19:48:10 Re: COMMIT NOWAIT Performance Option
Previous Message Bruce Momjian 2007-02-28 19:35:09 Re: COMMIT NOWAIT Performance Option