From: | Les <nagylzs(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: invalid value for parameter "default_text_search_config": "public.pg" |
Date: | 2023-07-22 07:29:51 |
Message-ID: | CAKXe9UDEjSj4wyMU4pj+f=7AnQAJwcw4Msx1DFGTXXbL_9nuDw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
>
> > I'm not sure what applied="public.pg", error="setting could not be
> applied"
> > means.
>
> No, "applied" is "f" (false), meaning that the setting is not actually
> usable.
> I'm a little surprised that it seems to have gotten into your live session
> anyway, although perhaps that's because the postmaster can't really
> validate it at startup.
>
> > I can change it in the config file, no problem. I just would like to
> > know if this is a simple configuration error, or a software installation
> > error. (Is public.pg a built-in config that should always exist?)
>
> "public.pg" is certainly not a standard (as in built-in) text search
> configuration name. Maybe that value was installed by some bit of
> software that failed to install the configuration to go with it,
> or only put the configuration into one database not everywhere in
> your installation?
>
All right, then it means that this is a configuration error, and it is not
a problem with the database instance and its live data. That was my main
concern. I'll just simply change this in the conf file and reload the
config.
This is all I needed, thank you for your help!
Laszlo
From | Date | Subject | |
---|---|---|---|
Next Message | De Lan | 2023-07-22 17:11:37 | Duplicate Primary keys in postgresql tables |
Previous Message | Tom Lane | 2023-07-21 21:09:15 | Re: invalid value for parameter "default_text_search_config": "public.pg" |