| From: | didier <did447(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: WALWriter active during recovery |
| Date: | 2014-12-17 15:56:25 |
| Message-ID: | CAJRYxuJb-QTwh5K6H9PyXr8=XNKzS5R_i3GBtuCH=8wE=HTDAQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi
On Wed, Dec 17, 2014 at 2:39 PM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> didier wrote:
>
>> On many Linux systems it may not do that much (2.6.32 and 3.2 are bad,
>> 3.13 is better but still it slows the fsync).
>>
>> If there's a fsync in progress WALReceiver will:
>> 1- slow the fsync because its writes to the same file are grabbed by the fsync
>> 2- stall until the end of fsync.
>
> Is this behavior filesystem-dependent?
I don't know. I only tested ext4
Attach the trivial code I used, there's a lot of junk in it.
Didier
| Attachment | Content-Type | Size |
|---|---|---|
| testf1.c | text/x-csrc | 3.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Teodor Sigaev | 2014-12-17 15:56:48 | Re: speedup tidbitmap patch: cache page |
| Previous Message | Alex Shulgin | 2014-12-17 15:50:15 | Re: REVIEW: Track TRUNCATE via pgstat |