Re: How to make sure I don't write a corrupt page to db when I checkpoint?
From: Brian Selzer <brian_at_selzer-software.com>
Date: Sun, 01 Jul 2007 14:15:28 GMT
Message-ID: <4GOhi.16530$2v1.15009_at_newssvr14.news.prodigy.net>
Date: Sun, 01 Jul 2007 14:15:28 GMT
Message-ID: <4GOhi.16530$2v1.15009_at_newssvr14.news.prodigy.net>
"Sune" <sune_ahlgren_at_hotmail.com> wrote in message
news:1183298186.773293.165890_at_z28g2000prd.googlegroups.com...
>
>>
>> What you want is for the application to bomb out with a general
>> protection
>> fault when it tries to access memory owned by the DB. Separate the
>> in-memory DB into its own process.
>>
>
> But I want to let the DB share its memory with application processes
> for performance reasons. So the app processes must be allowed to
> access the memory.
>
Then you run the risk of corruption.
> Hmmm...or am I missing something?
>
> Sorry if my initial post was confusing
> /Sune
>
Received on Sun Jul 01 2007 - 16:15:28 CEST