Skip site navigation (1) Skip section navigation (2)

Re: lazy_truncate_heap()

From: Greg Stark <greg(dot)stark(at)enterprisedb(dot)com>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: lazy_truncate_heap()
Date: 2008-12-31 19:45:18
Message-ID: 3DF8A552-B9BD-4496-88FE-55D1309BB25A@enterprisedb.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On 31 Dec 2008, at 13:21, Simon Riggs <simon(at)2ndQuadrant(dot)com> wrote:
>
> Both of these bugs are minor, but the effect of either/both of them is
> to cause more AccessExclusiveLocks than we might expect.
>
> For Hot Standby this means that many VACUUMs take AccessExclusiveLocks
> on relations, which would potentially lead to having queries cancelled
> for no reason at all.

Well by default it would just cause wal to pause briefly until the  
queries with those locks finish, no?

In response to

Responses

pgsql-hackers by date

Next:From: Heikki LinnakangasDate: 2008-12-31 19:45:20
Subject: Re: lazy_truncate_heap()
Previous:From: Alvaro HerreraDate: 2008-12-31 19:41:54
Subject: Re: reloptions and toast tables

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group