Re: WAL Rate Limiting

From: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: Andres Freund <andres(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: WAL Rate Limiting
Date: 2014-01-17 15:34:10
Message-ID: 52D94D72.1070308@vmware.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 01/17/2014 05:20 PM, Simon Riggs wrote:
> + if (RelationNeedsWAL(indexrel))
> + CHECK_FOR_WAL_BUDGET();

I don't think we need the RelationNeedsWAL tests. If the relation is not
WAL-logged, you won't write much WAL, so you should easily stay under
the limit. And CHECK_FOR_WAL_BUDGET() better be cheap when you're below
the limit.

- Heikki

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mel Gorman 2014-01-17 15:37:55 Re: [Lsf-pc] Linux kernel impact on PostgreSQL performance
Previous Message Heikki Linnakangas 2014-01-17 15:30:58 Re: WAL Rate Limiting