| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: WalSndWakeup() and synchronous_commit=off |
| Date: | 2012-06-07 23:42:22 |
| Message-ID: | CA+U5nMLytrCyMuNaryhU_qGB9dF90v+vG-RvHPoZcL7T5q-NwA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 7 June 2012 21:08, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
>> Moved the wakeup to a logical place outside a critical section.
> Hm. I don't really like the way you implemented that. While it reduces the
> likelihood quite a bit it will still miss wakeups if an XLogInsert pushes out
> the data because of missing space or if any place does an XLogFlush(lsn).
> The knowledge is really only available in XLogWrite...
Right, but the placement inside the critical section was objected to.
This way, any caller of XLogFlush() will be swept up at least once per
wal_writer_delay, so missing a few calls doesn't mean we have spikes
in replication delay.
Doing it more frequently was also an objection from Fujii, to which we
must listen.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2012-06-07 23:45:40 | Re: slow dropping of tables, DropRelFileNodeBuffers, tas |
| Previous Message | Robert Haas | 2012-06-07 23:25:20 | Re: New Postgres committer: Kevin Grittner |