| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Greg Stark <greg(dot)stark(at)enterprisedb(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: lazy_truncate_heap() |
| Date: | 2009-01-01 17:16:08 |
| Message-ID: | 1230830168.4032.92.camel@ebony.2ndQuadrant |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 2008-12-31 at 14:45 -0500, Greg Stark wrote:
> 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?
Yes, but why allow pointless actions in the first place?
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2009-01-01 17:54:33 | Re: lazy_truncate_heap() |
| Previous Message | Robert Haas | 2009-01-01 13:42:42 | Re: TODO items for window functions |