| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Re: [COMMITTERS] pgsql: Checkpointer starts before bgwriter to avoid missing fsync reque |
| Date: | 2012-06-01 13:49:39 |
| Message-ID: | CA+U5nMKsPed8+YeQSZCtYrbM-vuMwkGEPUE1Lu23Zy0rrHUjFw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On 1 June 2012 14:29, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Surely that commit is useless. Fsync requests go into a queue in shared
> memory, which had better have been set up by the postmaster. There is
> no requirement that the receiving process exist before somebody can put
> a request into the queue. If the queue overflows, the requestor has to
> take care of the fsync itself, but that is independent of whether the
> checkpointer is running yet.
The problem I saw was about fsync queue message overflow, not actually
missing fsyncs, so perhaps I worded the commit message poorly.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-06-01 13:59:23 | Re: Re: [COMMITTERS] pgsql: Checkpointer starts before bgwriter to avoid missing fsync reque |
| Previous Message | Tom Lane | 2012-06-01 13:29:17 | Re: Re: [COMMITTERS] pgsql: Checkpointer starts before bgwriter to avoid missing fsync reque |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-06-01 13:52:59 | Re: pg_upgrade from 9.0.7 to 9.1.3: duplicate key pg_authid_oid_index |
| Previous Message | Tom Lane | 2012-06-01 13:45:54 | Re: 9.2beta1, parallel queries, ReleasePredicateLocks, CheckForSerializableConflictIn in the oprofile |