From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | tushar <tushar(dot)ahuja(at)enterprisedb(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Andreas Seltenreich <seltenreich(at)gmx(dot)de> |
Subject: | Re: parallel worker (PID ) exited with exit code 1 |
Date: | 2017-10-06 13:02:48 |
Message-ID: | CAB7nPqQkzHKQyBkPPL9V4o+EJttAFrrJS2mEyo5hDaZm5QOnLA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Oct 6, 2017 at 9:19 PM, tushar <tushar(dot)ahuja(at)enterprisedb(dot)com> wrote:
> 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
pg_wal_replay_pause() is a function marked as PARALLEL SAFE, meaning
that it can be pushed down to parallel workers. Still, it can only be
executed on standbys, so this would correctly fail with the error you
are seeing here on a primary server. Perhaps there is a way to
blacklist some functions depending on the server context. This
question may be better asked directly where the project is maintained
then: https://github.com/anse1/sqlsmith. I am adding as well Andreas
in CC, he works on sqlsmith.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2017-10-06 13:06:08 | Re: Proposal: Improve bitmap costing for lossy pages |
Previous Message | Ashutosh Bapat | 2017-10-06 12:40:59 | Re: Partition-wise join for join between (declaratively) partitioned tables |