Re: question regarding full_page_write

From: Martín Marqués <martin(dot)marques(at)gmail(dot)com>
To: Greg Smith <greg(at)2ndquadrant(dot)com>
Cc: AI Rumman <rummandba(at)gmail(dot)com>, pgsql-general General <pgsql-general(at)postgresql(dot)org>
Subject: Re: question regarding full_page_write
Date: 2011-08-22 21:07:51
Message-ID: CABeG9Lu5zJoNaCcR0M=jgP8A7b5Dbc70VOW_genTGnMiAr8EYw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

2011/2/17 Greg Smith <greg(at)2ndquadrant(dot)com>:
> AI Rumman wrote:
>>
>> I can't clearly understand what FULL_PAGE_WRITE parameter is stand for.
>> Documentation suggest that If I make it OFF, then I have the chance for DB
>> crash.
>> Can anyone please tell me how it could be happened?
>
> The database writes to disk in 8K blocks.  If you can be sure that your disk
> drives and operating system will always write in 8K blocks, you can get a
> performance improvement from turning full_page_writes off.  But if you do
> that, and it turns out that when the power is interrupted your disk setup
> will actually do partial writes of less than 8K, your database can get
> corrupted.  Your system needs to ensure that when a write happens, either
> the whole thing goes to disk, or none of it does.

Sorry for the late reply, but I was investigating this option in
postgresql.conf and saw this mail.

My question regarding your answer is, why is it important for the
first page after a checkpoint and not on other page writes?

--
Martín Marqués
select 'martin.marques' || '@' || 'gmail.com'
DBA, Programador, Administrador

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Greg Smith 2011-08-22 21:39:54 Re: question regarding full_page_write
Previous Message Gary Chambers 2011-08-22 18:20:00 Re: securing the sql server ?