On Thu, 17 Nov 2005 [EMAIL PROTECTED] wrote:
>
>>
>> Database corruption is uncommon. The usual causes are
>>
>> (1) Running with synchronous=OFF
>
>Which just about sums it up!
>
>But, a question, I assume there is no risk if you are only using
>selects, i.e. the db is read only. Is there any
On 11/17/2005 at 00:54 Preston Z wrote:
>
>Anybody have a better way to tell if a db is garbage?
You will know in the real world because things don't work randomly and
the users will complain.
My experience is like yours, a corrupt database can be worked with much
like a normal one so long as
At 00:54 17/11/2005, Preston Z wrote:
If the power never goes out and no programs ever crash on you system then
Synchronous = OFF is for you, but the rest of the world might still want
it ON. Really it sounds like the thing you need to worry about most is the
unexpected termination of your
>
> Database corruption is uncommon. The usual causes are
>
> (1) Running with synchronous=OFF
Which just about sums it up!
But, a question, I assume there is no risk if you are only using
selects, i.e. the db is read only. Is there any performance advantage
in having synchronous off in
"Preston Z" <[EMAIL PROTECTED]> wrote:
> If the power never goes out and no programs ever crash on you system then
> Synchronous = OFF is for you, but the rest of the world might still want it
> ON.
Minor clarification: Program crashes will not cause data corruption with
synchronous=off. But
If the power never goes out and no programs ever crash on you system then
Synchronous = OFF is for you, but the rest of the world might still want it
ON. Really it sounds like the thing you need to worry about most is the
unexpected termination of your program. If you aren't worried about
6 matches
Mail list logo
