Re: Sudden FTS-related error from parallel worker in 9.6

From: Nikolay Samokhvalov <samokhvalov(at)gmail(dot)com>
To: David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>
Cc: PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Sudden FTS-related error from parallel worker in 9.6
Date: 2016-10-04 04:20:39
Message-ID: CANNMO+KKNTmKAb6r4bjV5_13Qv8G6UJLe2fnxFzO5wMHphtDEA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Oct 4, 2016 at 6:33 AM, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>
wrote:
>
> The reason that you receive this message is that the main process must
> serialise all GUC settings into text before passing to the worker
> processes, and when the worker receive those serialised settings from
> the master, it must apply them so that workers behave the same way as
> the main process.
>

Thanks for the explanation. I understand that it's side-effect, but
nevertheless it's a bug leading to inability to use parallelization and it
can break some applications.

>
> Probably the question here is why is the worker process validating the
> GUC when it was not validated when postgresql.conf is loaded
>

Yes, the question is why the behavior is different. I also noticed that if
I set default_text_search_config in postgresql.conf, I don't get warning
when starting psql:

postgres(at)dev:~$ psql test
Timing is on.
psql (9.6.0)
Type "help" for help.

But again, if I alter database test, setting the same option, I get the
warning:

postgres(at)dev:~$ psql test
WARNING: invalid value for parameter "default_text_search_config": "ru"
Timing is on.
psql (9.6.0)
Type "help" for help.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Devrim Gündüz 2016-10-04 04:57:55 Re: Sudden FTS-related error from parallel worker in 9.6
Previous Message David Rowley 2016-10-04 03:33:45 Re: Sudden FTS-related error from parallel worker in 9.6