Re: dsa_allocate() faliure

2019-02-18 Thread Jakub Glapa
Hi I just checked the dmesg. The segfault I wrote about is the only one I see, dated Nov 24 last year. Since then no other segfaults happened although dsa_allocated failures happen daily. I'll report if anything occurs. I have the core dumping setup in place. -- regards, pozdrawiam, Jakub

Re: dsa_allocate() faliure

2019-02-03 Thread Jakub Glapa
ave to run this with prod data. My question is. Can I do anything like increasing logging level or enable some additional options? It's a production server but I'm willing to sacrifice a bit of it's performance if that would help. -- regards, pozdrawiam, Jakub Glapa On Wed, Jan 30

Re: dsa_allocate() faliure

2018-11-26 Thread Jakub Glapa
Justin thanks for the information! I'm running Ubuntu 16.04. I'll try to prepare for the next crash. Couldn't find anything this time. -- regards, Jakub Glapa On Mon, Nov 26, 2018 at 4:52 PM Justin Pryzby wrote: > Hi, thanks for following through. > > On Mon, Nov 26,

Re: dsa_allocate() faliure

2018-11-26 Thread Jakub Glapa
rds, pozdrawiam, Jakub Glapa On Mon, Nov 26, 2018 at 4:26 PM Jakub Glapa wrote: > So, the issue occurs only on production db an right now I cannot reproduce > it. > I had a look at dmesg and indeed I see something like: > > > -- > regards, > Jakub Glapa > > > On Fri

Re: dsa_allocate() faliure

2018-11-26 Thread Jakub Glapa
So, the issue occurs only on production db an right now I cannot reproduce it. I had a look at dmesg and indeed I see something like: -- regards, pozdrawiam, Jakub Glapa On Fri, Nov 23, 2018 at 5:10 PM Justin Pryzby wrote: > On Fri, Nov 23, 2018 at 03:31:41PM +0100, Jakub Glapa wrote: >

Re: dsa_allocate() faliure

2018-11-23 Thread Jakub Glapa
ver is alive): psql db@host as user => set max_parallel_workers=0; SET Time: 89.542 ms psql db@host as user => SELECT ; FATAL: XX000: dsa_allocate could not find 7 free pages LOCATION: dsa_allocate_extended, dsa.c:729 SSL connection has been closed unexpectedly The connection to the server was lo

Re: dsa_allocate() faliure

2018-11-21 Thread Jakub Glapa
Looks like my email didn't match the right thread: https://www.postgresql.org/message-id/flat/CAMAYy4%2Bw3NTBM5JLWFi8twhWK4%3Dk_5L4nV5%2BbYDSPu8r4b97Zg%40mail.gmail.com Any chance to get some feedback on this? -- regards, Jakub Glapa On Tue, Nov 13, 2018 at 2:08 PM Jakub Glapa wrote: >

Re: dsa_allocate() faliure

2018-11-13 Thread Jakub Glapa
dims ? 'p'::text) AND (dims ? 'mcp'::text)) OR ((datasource)::text = ANY ('{"FA","GA"}'::text[]))) AND (c_id = ANY (''::bigint[]))) -> Parallel Seq Scan on fa_106 (cost=0.00..11.99 rows=1 width=580) Filter: ((datetime >= '2018-01-01 00:00:00+01'::timestamp with time zone) AND ((datasource)::text <> 'M'::text) AND (((dims ? 'p'::text) AND (dims ? 'mcp'::text)) OR ((datasource)::text = ANY ('{"FA","GA"}'::text[]))) AND (c_id = ANY ('.. -- regards, Jakub Glapa