Re: ERROR: too many dynamic shared memory segments

2017-12-07 Thread Jakub Glapa
Thank You Thomas! -- regards, Jakub Glapa On Thu, Dec 7, 2017 at 10:30 PM, Thomas Munro wrote: > On Tue, Dec 5, 2017 at 1:18 AM, Jakub Glapa wrote: > > I see that the segfault is under active discussion but just wanted to > ask if > > increasing the max_connections to miti

Re: ERROR: too many dynamic shared memory segments

2017-12-04 Thread Jakub Glapa
I see that the segfault is under active discussion but just wanted to ask if increasing the max_connections to mitigate the DSM slots shortage is the way to go? -- regards, Jakub Glapa On Mon, Nov 27, 2017 at 11:48 PM, Thomas Munro < thomas.mu...@enterprisedb.com> wrote: > On Tu

Re: ERROR: too many dynamic shared memory segments

2017-11-27 Thread Jakub Glapa
:192.168.10.83(35300):user@db:[30152]: FATAL: the database system is in recovery mode -- regards, pozdrawiam, Jakub Glapa On Mon, Nov 27, 2017 at 7:53 PM, Thomas Munro wrote: > On Tue, Nov 28, 2017 at 1:13 AM, Jakub Glapa > wrote: > > The queries are somehow special. > >

Re: ERROR: too many dynamic shared memory segments

2017-11-27 Thread Jakub Glapa
rce)::text = 'two'::text) -> Bitmap Index Scan on par_7_datasource (cost=0.00..4.36 rows=10 width=0) Index Cond: ((datasource)::text = 'three'::text) I

ERROR: too many dynamic shared memory segments

2017-11-27 Thread Jakub Glapa
= 8GB min_wal_size = 4GB checkpoint_completion_target = 0.9 wal_buffers = 32MB default_statistics_target = 1000 max_locks_per_transaction = 128 #max_parallel_workers_per_gather = 0 PS. I've posted this question on pgsql-admin distro but didn't get any feedback. -- regards, Jakub Glapa