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

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: [HACKERS] parallel worker (PID ) exited with exit code 1
Дата
Msg-id CAB7nPqQkzHKQyBkPPL9V4o+EJttAFrrJS2mEyo5hDaZm5QOnLA@mail.gmail.com
обсуждение исходный текст
Ответ на [HACKERS] parallel worker (PID ) exited with exit code 1  (tushar <tushar.ahuja@enterprisedb.com>)
Ответы Re: [HACKERS] parallel worker (PID ) exited with exit code 1  (Andreas Seltenreich <seltenreich@gmx.de>)
Список pgsql-hackers
On Fri, Oct 6, 2017 at 9:19 PM, tushar <tushar.ahuja@enterprisedb.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


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Ashutosh Bapat
Дата:
Сообщение: Re: [HACKERS] Partition-wise join for join between (declaratively)partitioned tables
Следующее
От: Robert Haas
Дата:
Сообщение: Re: [HACKERS] Proposal: Improve bitmap costing for lossy pages