Re: pg11.1: dsa_area could not attach to segment

Поиск
Список
Период
Сортировка
Искать
От
Justin Pryzby
Тема
Re: pg11.1: dsa_area could not attach to segment
Дата
Msg-id
20190206185241.GF29720@telsasoft.com
Ответ на
Список
Дерево обсуждения
pg11.1: dsa_area could not attach to segment Justin Pryzby <pryzby@telsasoft.com>
Re: pg11.1: dsa_area could not attach to segment Justin Pryzby <pryzby@telsasoft.com>
Re: pg11.1: dsa_area could not attach to segment Justin Pryzby <pryzby@telsasoft.com>
Re: pg11.1: dsa_area could not attach to segment Justin Pryzby <pryzby@telsasoft.com>
Re: pg11.1: dsa_area could not attach to segment Thomas Munro <thomas.munro@enterprisedb.com>
Re: pg11.1: dsa_area could not attach to segment Justin Pryzby <pryzby@telsasoft.com>
Re: pg11.1: dsa_area could not attach to segment Sergei Kornilov <sk@zsrv.org>
Re: pg11.1: dsa_area could not attach to segment Jakub Glapa <jakub.glapa@gmail.com>
Re: pg11.1: dsa_area could not attach to segment Justin Pryzby <pryzby@telsasoft.com>
Re: pg11.1: dsa_area could not attach to segment Jakub Glapa <jakub.glapa@gmail.com>
Re: pg11.1: dsa_area could not attach to segment Thomas Munro <thomas.munro@enterprisedb.com>
Re: pg11.1: dsa_area could not attach to segment Thomas Munro <thomas.munro@enterprisedb.com>
On Wed, Feb 06, 2019 at 06:37:16PM +0100, Jakub Glapa wrote:
> I'm seeing dsa_allocate on two different servers.
> One is virtualized with VMWare the other is bare metal.

Thanks.  So it's not limited to vmware or VM at all.

FYI here we've seen DSA errors on (and only on) two vmware VMs.

It might be interesting to have CPU info, too.

For us the affected servers are:

Intel(R) Xeon(R) CPU E5-2470 0 @ 2.30GHz stepping 02
microcode: CPU0 sig=0x206d2, pf=0x1, revision=0xb00002e

Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz stepping 02
microcode: CPU0 sig=0x206d2, pf=0x1, revision=0x710

В списке pgsql-hackers по дате отправления
От: Sergei Kornilov
Дата:
От: Ibrar Ahmed
Дата:
FAQ