Re: Hard limit on WAL space used (because PANIC sucks)

From: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)2ndquadrant(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Peter Geoghegan <pg(at)heroku(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: Hard limit on WAL space used (because PANIC sucks)
Date: 2014-01-22 12:14:27
Message-ID: 52DFB623.8080206@vmware.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 01/22/2014 02:10 PM, Simon Riggs wrote:
> As Jeff points out, the blocks being modified would be locked until
> space is freed up. Which could make other users wait. The code
> required to avoid that wait would be complex and not worth any
> overhead.

Checkpoint also acquires the content lock of every dirty page in the
buffer cache...

- Heikki

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Korotkov 2014-01-22 12:17:43 Re: GIN improvements part 1: additional information
Previous Message Heikki Linnakangas 2014-01-22 12:12:20 GIN pending list pages not recycled promptly (was Re: GIN improvements part 1: additional information)