From: Justin Pryzby <pryzby@telsasoft.com>
To: Jakub Glapa <jakub.glapa@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: dsa_allocate() faliure
Date: Fri, 23 Nov 2018 10:10:28 -0600
Message-ID: <20181123161028.GL10913@telsasoft.com> (raw)
In-Reply-To: <CAJk1zg3nCqG2fo_vg2RwOW6s4TjKnnnqDTrFN4FQMVAT5XEbMQ@mail.gmail.com>
References: <CAJk1zg0x881aTwbEM8d-5EWVPfVWxN+Z56+parZ1WFc5DVcgmA@mail.gmail.com>
<CAJk1zg10iCNsxFvQ4pgKe1B0rdjNG9iELA7AzLXjXnQm5T=KzQ@mail.gmail.com>
<20181122160958.GJ10913@telsasoft.com>
<CAJk1zg3nCqG2fo_vg2RwOW6s4TjKnnnqDTrFN4FQMVAT5XEbMQ@mail.gmail.com>
On Fri, Nov 23, 2018 at 03:31:41PM +0100, Jakub Glapa wrote:
> Hi Justin, I've upgrade to 10.6 but the error still shows up:
>
> If I set it to max_parallel_workers=0 I also get and my connection is being
> closed (but the server is alive):
>
> psql db@host as user => set max_parallel_workers=0;
Can you show the plan (explain without analyze) for the nonparallel case?
Also, it looks like the server crashed in that case (even if it restarted
itself quickly). Can you confirm ?
For example: dmesg |tail might show "postmaster[8582]: segfault [...]" or
similar. And other clients would've been disconnected. (For example, you'd
get an error in another, previously-connected session the next time you run:
SELECT 1).
In any case, could you try to find a minimal way to reproduce the problem ? I
mean, is the dataset and query small and something you can publish, or can you
reproduce with data generated from (for example) generate_series() ?
Thanks,
Justin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: pryzby@telsasoft.com, jakub.glapa@gmail.com
Subject: Re: dsa_allocate() faliure
In-Reply-To: <20181123161028.GL10913@telsasoft.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox