From: | kjonca(at)fastmail(dot)com (Kamil Jońca ) |
---|---|
To: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: backend crash |
Date: | 2020-04-13 16:02:34 |
Message-ID: | 87o8rv5q79.fsf@alfa.kjonca |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | Postg롤 토토SQL : Postg롤 토토SQL 메일 링리스트 : 2020-04-13 이후 PGSQL-BUGS 16:02 |
Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> writes:
> On Mon, Apr 13, 2020 at 11:01:01AM -0400, Tom Lane wrote:
>>Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> writes:
>>> On Mon, Apr 13, 2020 at 09:25:35AM +0200, Kamil Jońca wrote:
>>>> I have problem with (pseudo) random backend crashes.
>>>> They seems to happen at one query, but not every time.
>>
>>> I've tried to reproduce this, but unfortunately it does not fail for me.
>>> Chances are this depends on data. Can you prepare a small data sample
>>> that would trigger the issue?
>>
>>This is evidently a parallel-query worker, so it's unlikely you'd ever
>>get anywhere near this crash with a "small" data sample; for starters
>>there'd have to be enough data to prompt use of a parallel plan.
>>
>>I doubt that the crash is very data-specific though. Maybe just fill
>>the table with a lot of dummy data?
>>
>
> I did that, of course, and the plan looks like this:
>
1. Did you try run this many times? As I wrote this does not crash every
time. I can reproduce this on my data by running query 1000 times in
loop.
2. I can try to prepare test data, but it will be rather long
process. Stay tuned :/
KJ
--
http://stopstopnop.pl/stop_stopnop.pl_o_nas.html
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2020-04-13 16:19:13 | Re: backend crash |
Previous Message | PG Bug reporting form | 2020-04-13 16:00:36 | BUG #16359: Server error message: ERROR: memory exhausted |