Re: BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker

On Tue, Apr 2, 2019 at 12:24 AM PG Bug reporting form
<noreply(at)postgresql(dot)org> wrote:
> default_text_search_config = '' #default 'pg_catalog.simple'

That causes problems for parallel workers. The stack looks like this:

frame #3: 0x00000001007772d9
postgres`errfinish(dummy=<unavailable>) at elog.c:552:3 [opt]
frame #4: 0x00000001007082ab
postgres`stringToQualifiedNameList(string=<unavailable>) at
regproc.c:0:3 [opt]
frame #5: 0x0000000100773995
postgres`check_TSCurrentConfig(newval=0x00007ffeef918850,
extra=<unavailable>, source=PGC_S_ARGV) at ts_cache.c:603:29 [opt]
frame #6: 0x0000000100793bc5
postgres`call_string_check_hook(conf=0x00000001009d04f8,
newval=0x00007ffeef918850, extra=<unavailable>, source=<unavailable>,
elevel=20) at guc.c:10611:7 [opt]
frame #7: 0x00000001007933f1
postgres`parse_and_validate_value(record=0x00000001009d04f8,
name=<unavailable>, value=<unavailable>, source=PGC_S_ARGV, elevel=20,
newval=0x00007ffeef918850, newextra=0x00007ffeef918848) at
guc.c:6544:10 [opt]
frame #8: 0x00000001007918ea
postgres`set_config_option(name="default_text_search_config",
value="\x03", context=<unavailable>, source=PGC_S_ARGV,
action=GUC_ACTION_SET, changeVal=<unavailable>, elevel=17973805,
is_reload=<unavailable>) at guc.c:7147:11 [opt]
frame #9: 0x00000001007990ce
postgres`RestoreGUCState(gucstate=<unavailable>) at guc.c:10065:12
[opt]
frame #10: 0x0000000100382e9b
postgres`ParallelWorkerMain(main_arg=<unavailable>) at
parallel.c:1360:2 [opt]

Why is the empty string acceptable to the master but not with
RestoreGUCState() in a parallel worker?

--
Thomas Munro
https://enterprisedb.com