pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tomas Vondra <tomas.vondra@2ndquadrant.com>
To: Kamil Jońca <kjonca@fastmail.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: backend crash
Date: Mon, 13 Apr 2020 13:41:47 +0200
Message-ID: <20200413114147.a42vf3tr3auybdtr@development> (raw)
In-Reply-To: <87imi37spc.fsf@alfa.kjonca>
References: <87imi37spc.fsf@alfa.kjonca>

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





view thread (13+ messages)  latest in thread

Message-ID: <20200413114147.a42vf3tr3auybdtr@development>
Permalink:  ../20200413114147.a42vf3tr3auybdtr@development/
Also on:    postgresql.org/message-id/20200413114147.a42vf3tr3auybdtr@development

 · 

reply

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-bugs@postgresql.org
  Cc: tomas.vondra@2ndquadrant.com, kjonca@fastmail.com, pgsql-bugs@lists.postgresql.org
  Subject: Re: backend crash
  In-Reply-To: <20200413114147.a42vf3tr3auybdtr@development>

* 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