Re: BUG #5946: Long exclusive lock taken by vacuum (not full) - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: BUG #5946: Long exclusive lock taken by vacuum (not full)
Date
Msg-id 1301321082-sup-1641@alvh.no-ip.org
Whole thread Raw
In response to Re: BUG #5946: Long exclusive lock taken by vacuum (not full)  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: BUG #5946: Long exclusive lock taken by vacuum (not full)
Re: BUG #5946: Long exclusive lock taken by vacuum (not full)
List pgsql-bugs
Rainer, any idea?  Please see
http://archives.postgresql.org/message-id/4D906269.6060109@commandprompt.com


Excerpts from Alvaro Herrera's message of lun mar 28 11:03:16 -0300 2011:
> Excerpts from Alvaro Herrera's message of lun mar 28 07:26:49 -0300 2011:
> > Likely "too large" is more an issue related to available resources than
> > of absolute figure.
> >
> > On a penta byte of free storage I would not mind allocating some teras
> > with extending a (large) table.
> > If I'm left with some MB only, I'd be concerned for sure.
>
> ...
>
> Does anybody have an idea just W-T-F happened here?  I did NOT send the
> above email (as evidenced by it being signed by "Rainer").  I notice it
> even has a "@commandprompt.com" message-id.  Should I start signing my
> email?
>

--
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

pgsql-bugs by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: BUG #5946: Long exclusive lock taken by vacuum (not full)
Next
From: Rainer Pruy
Date:
Subject: Re: BUG #5946: Long exclusive lock taken by vacuum (not full)