Re: dsa_allocate() faliure

2019-02-07 Thread Jakub Glapa
s I have something. -- regards, pozdrawiam, Jakub Glapa On Thu, Feb 7, 2019 at 12:21 AM Justin Pryzby wrote: > Moving to -hackers, hopefully it doesn't confuse the list scripts too much. > > On Mon, Feb 04, 2019 at 08:52:17AM +0100, Jakub Glapa wrote: > > I see the error show

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

2019-02-06 Thread Jakub Glapa
> > 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

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

2019-02-06 Thread Jakub Glapa
:~$ sudo dmidecode -s system-product-name ProLiant DL380 Gen9 -- regards, pozdrawiam, Jakub Glapa On Wed, Feb 6, 2019 at 6:19 PM Justin Pryzby wrote: > On Wed, Feb 06, 2019 at 04:22:12PM +1100, Thomas Munro wrote: > > Can anyone else who has hit this comment on any virtualisation they

Re: dsa_allocate() faliure

2018-11-30 Thread Jakub Glapa
in parallel from 2-3 sessions. Sometimes it was breaking sometimes not. Couldn't find any pattern. The workload on this db is not really constant, rather bursting. -- regards, Jakub Glapa On Tue, Nov 27, 2018 at 9:03 AM Thomas Munro wrote: > On Tue, Nov 27, 2018 at 4:00 PM Thomas Munro >