From: | Jim Nasby <jnasby(at)pervasive(dot)com> |
---|---|
To: | Clodoaldo Pinto <clodoaldo(dot)pinto(at)gmail(dot)com> |
Cc: | "pgsql-general postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: How to build with bigger WAL segment file? |
Date: | 2006-06-22 19:46:10 |
Message-ID: | 7758C807-D7B3-4B65-BE6E-816A62FC5D41@pervasive.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Jun 19, 2006, at 4:10 PM, Clodoaldo Pinto wrote:
> 2006/6/19, Clodoaldo Pinto <clodoaldo(dot)pinto(at)gmail(dot)com>:
>> Since I have a database with a frequent and huge update batch, the
>> WAL
>> segment file number is about 130. I suspect these files management
>> during the update is hurting performance. Is it likely? I'm using
>> Fedora Core 3 and checkpoint_segments is set to 64.
>>
>> To overcome this I'm considering to make the WAL segment files
>> bigger.
>> The segment file default size is 16 MB. How to build from the source
>> rpm to have bigger files, say 128 MB?
>>
>
> I found it in src/include/pg_config_manual.h:
BTW, someone (Mark Wong?) recently posted some performance testing
results from upping XLOG_SEG_SIZE... take a look in the archives.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
From | Date | Subject | |
---|---|---|---|
Next Message | Guy Rouillier | 2006-06-22 19:51:06 | Re: sql question; checks if data already exists before inserted |
Previous Message | Joshua D. Drake | 2006-06-22 19:46:01 | Re: OT: publicly available databases? |