Re: pg11.1: dsa_area could not attach to segment
| От | Jakub Glapa |
|---|---|
| Тема | Re: pg11.1: dsa_area could not attach to segment |
| Дата | |
| Msg-id | CAJk1zg2rO7Sv=vmZKGiDzco6p1imd=nh6ToYrNj8sBru8-LOHw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: pg11.1: dsa_area could not attach to segment (Justin Pryzby <pryzby@telsasoft.com>) |
| Список | pgsql-hackers |
It might be interesting to have CPU info, too.
model name : Intel(R) Xeon(R) CPU E5-2637 v4 @ 3.50GHz (virtualized vmware)
and
model name : Intel(R) Xeon(R) CPU E5-2667 v3 @ 3.20GHz (bare metal)
--
regards,
pozdrawiam,
Jakub Glapa
On Wed, Feb 6, 2019 at 7:52 PM Justin Pryzby <pryzby@telsasoft.com> wrote:
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 по дате отправления: