Re: lazy_truncate_heap() - Mailing list pgsql-hackers

From Greg Stark
Subject Re: lazy_truncate_heap()
Date
Msg-id 3DF8A552-B9BD-4496-88FE-55D1309BB25A@enterprisedb.com
Whole thread Raw
In response to lazy_truncate_heap()  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: lazy_truncate_heap()  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Re: lazy_truncate_heap()  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
On 31 Dec 2008, at 13:21, Simon Riggs <simon@2ndQuadrant.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?


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: lazy_truncate_heap()
Next
From: Stephen Frost
Date:
Subject: Re: pg_dump roles support [Review]