| From: | tgl(at)postgresql(dot)org (Tom Lane) |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: Rearrange mdsync() looping logic to avoid the problem that a |
| Date: | 2007-04-12 17:10:55 |
| Message-ID: | 20070412171055.5BBFE9FA399@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Log Message:
-----------
Rearrange mdsync() looping logic to avoid the problem that a sufficiently
fast flow of new fsync requests can prevent mdsync() from ever completing.
This was an unforeseen consequence of a patch added in Mar 2006 to prevent
the fsync request queue from overflowing. Problem identified by Heikki
Linnakangas and independently by ITAGAKI Takahiro; fix based on ideas from
Takahiro-san, Heikki, and Tom.
Back-patch as far as 8.1 because a previous back-patch introduced the problem
into 8.1 ...
Modified Files:
--------------
pgsql/src/backend/storage/smgr:
md.c (r1.127 -> r1.128)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/smgr/md.c.diff?r1=1.127&r2=1.128)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-04-12 17:11:00 | pgsql: Rearrange mdsync() looping logic to avoid the problem that a |
| Previous Message | User Dpage | 2007-04-12 16:54:36 | pginstaller - pginst: Lose the PGDIR variable - assume PostgreSQL is |