Re: parallel worker (PID ) exited with exit code 1

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: tushar <tushar(dot)ahuja(at)enterprisedb(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: parallel worker (PID ) exited with exit code 1
Date: 2017-10-06 13:11:10
Message-ID: CA+TgmoajhtR91ApxvbbxsngOoZSgwFuoHXPuEMjBxpAptKjQAw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Oct 6, 2017 at 8:19 AM, tushar <tushar(dot)ahuja(at)enterprisedb(dot)com> wrote:
> I got some few queries after running sqlsmith against PG HEAD , where i am
> getting LOG message like - "parallel worker (PID) exited with exit code 1"
>
> set force_parallel_mode =1;
> select
> pg_catalog.pg_wal_replay_pause() as c0,
> ref_0.ev_type as c1
> from
> pg_catalog.pg_rewrite as ref_0
> where ref_0.ev_enabled > ref_0.ev_type
> limit 53;
>
> 2017-10-06 13:15:34.785 BST [5680] LOG: background worker "parallel worker"
> (PID 5964) exited with exit code 1
> ERROR: recovery is not in progress
> HINT: Recovery control functions can only be executed during recovery.
> CONTEXT: parallel worker

You seem to be assuming this is wrong, but I don't see what the
problem is. There's nothing unsafe about an error happening side of a
worker, and you got an error because this function isn't safe to
execute during normal running.

I would say this is a case of everything working as intended.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2017-10-06 13:18:30 Re: [COMMITTERS] pgsql: Fix freezing of a dead HOT-updated tuple
Previous Message Bernd Helmle 2017-10-06 13:08:13 Re: parallel worker (PID ) exited with exit code 1