| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
| Cc: | Kamil Jońca <kjonca(at)fastmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: backend crash |
| Date: | 2020-04-13 15:01:01 |
| Message-ID: | 394.1586790061@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | Postg토토 사이트 추천SQL : Postg토토 사이트 추천SQL 메일 링리스트 : 2020-04-13 이후 PGSQL-BUGS 15:01 |
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?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2020-04-13 15:32:46 | Re: backend crash |
| Previous Message | PG Bug reporting form | 2020-04-13 14:58:29 | BUG #16358: formas web site sql |