| From: | Bernd Helmle <mailings(at)oopsware(dot)de> |
|---|---|
| To: | tushar <tushar(dot)ahuja(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: parallel worker (PID ) exited with exit code 1 |
| Date: | 2017-10-06 13:08:13 |
| Message-ID: | 1507295293.3833.6.camel@oopsware.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Am Freitag, den 06.10.2017, 17:49 +0530 schrieb tushar:
> 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;
Looks like pg_wal_replay_pause() is marked as parallel safe:
SELECT proparallel FROM pg_proc WHERE proname = 'pg_wal_replay_pause';
-[ RECORD 1 ]--
proparallel | s
Bernd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-10-06 13:11:10 | Re: parallel worker (PID ) exited with exit code 1 |
| Previous Message | Robert Haas | 2017-10-06 13:06:08 | Re: Proposal: Improve bitmap costing for lossy pages |