| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Rob Wultsch <wultsch(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Jim Nasby <jim(at)nasby(dot)net>, flyusa2010 fly <flyusa2010(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Can postgres create a file with physically continuous blocks. |
| Date: | 2010-12-22 07:29:01 |
| Message-ID: | 4D11A8BD.7020204@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 22.12.2010 09:25, Rob Wultsch wrote:
> On Wed, Dec 22, 2010 at 12:15 AM, Heikki Linnakangas
> <heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
>> Hmm, innodb_autoextend_increment seems more like what we're discussing here
>> (http://dev.mysql.com/doc/refman/5.0/en/innodb-parameters.html#sysvar_innodb_autoextend_increment)
>> If I'm reading that correctly, InnoDB defaults to extending files in 8MB
>> chunks.
>
> This is not pure apples to apples as InnoDB does direct io, however
> doesn't the checkpoint completion target code call fsync repeatedly in
> order to achieve the check point completion target?
It only fsync's each file once. If there's a lot of files, it needs to
issue a lot of fsync's, but for different files.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sushant Sinha | 2010-12-22 12:44:43 | Re: bug in ts_rank_cd |
| Previous Message | Rob Wultsch | 2010-12-22 07:25:40 | Re: Can postgres create a file with physically continuous blocks. |