From: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
---|---|
To: | Kamil Jońca <kjonca(at)fastmail(dot)com> |
Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: backend crash |
Date: | 2020-04-13 11:41:47 |
Message-ID: | 20200413114147.a42vf3tr3auybdtr@development |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | Postg스포츠 토토 베트맨SQL : Postg스포츠 토토 베트맨SQL 메일 링리스트 : 2020-04-13 이후 PGSQL-BUGS |
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.
>
>table:
>
>--8<---------------cut here---------------start------------->8---
>CREATE TABLE digitalocean.log (
> ts timestamp with time zone DEFAULT now() NOT NULL,
> actions jsonb NOT NULL,
> account text NOT NULL
>);
>
>ALTER TABLE ONLY digitalocean.log
> ADD CONSTRAINT log_ts_key UNIQUE (ts);
>--8<---------------cut here---------------end--------------->8---
>
>query:
>--8<---------------cut here---------------start------------->8---
>with x as (select jsonb_array_elements (actions->'actions')->'id' as id ,ts from digitalocean.log where account='onet') select max(x.id::bigint) from x;
>--8<---------------cut here---------------end--------------->8---
>
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?
regards
--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Hunosau, Aliaksei | 2020-04-13 12:53:32 | pg_isready bug |
Previous Message | Kyotaro Horiguchi | 2020-04-13 08:36:10 | Re: BUG #16337: Finnish Ispell dictionary cannot be created |