Michael Paquier writes:
> On Fri, Oct 6, 2017 at 9:19 PM, tushar wrote:
>> ERROR: recovery is not in progress
>
> 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://githu
On Fri, Oct 6, 2017 at 8:19 AM, tushar 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,
>
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
On Fri, Oct 6, 2017 at 9:19 PM, tushar 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 wor
Hi,
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
