Re: stuck spinlock (0x2aac3678b0e0) detected at dynahash.c:876

Поиск
Список
Период
Сортировка
От Merlin Moncure
Тема Re: stuck spinlock (0x2aac3678b0e0) detected at dynahash.c:876
Дата
Msg-id b42b73150911200954t435ae7bajb10f5eb403b6b5ad@mail.gmail.com
обсуждение исходный текст
Ответ на stuck spinlock (0x2aac3678b0e0) detected at dynahash.c:876  (Matt Solnit <msolnit@soasta.com>)
Ответы Re: stuck spinlock (0x2aac3678b0e0) detected at dynahash.c:876  (Matt Solnit <msolnit@soasta.com>)
Список pgsql-general
On Fri, Nov 20, 2009 at 12:15 PM, Matt Solnit <msolnit@soasta.com> wrote:
>
> We are running PostgreSQL 8.3.8 (64-bit) on a dedicated Fedora Core 8 machine, in Amazon EC2.  This was using an
"extra-large"instance, which means 4 Xeon cores (2.66 GHz) and 15.5 GB of memory. 

considering that ec2 is a virtualized environment, the first
conclusion that everyone is going to jump to is that this is some type
of issue with ec2.  IIRC ec2 runs xen, did you search for any related
issues with xen and postgresql?

are you running the correct kernel?
http://developer.amazonwebservices.com/connect/entry.jspa?externalID=1535

"We strongly recommend using the 2.6.18 Xen stock kernel with the
c1.medium and c1.xlarge instances. Although the default Amazon EC2
kernels will work, the new kernels provide greater stability and
performance for these instance types. For more information about
kernels, refer to the Amazon Elastic Compute Cloud Developer Guide."

merlin

В списке pgsql-general по дате отправления:

Предыдущее
От: "Joshua D. Drake"
Дата:
Сообщение: Re: ora2pg and DBD::Pg
Следующее
От: Chris Barnes
Дата:
Сообщение: Is there a tool used to display statement times from postgres logs