Re: [Util] Warn and Remove Invalid GUCs
| От | Srinath Reddy Sadipiralla |
|---|---|
| Тема | Re: [Util] Warn and Remove Invalid GUCs |
| Дата | |
| Msg-id | CAFC+b6qmw5=KGLSxanGE5qAR+=r1mUhmfX34wvPQ5vc3uVr4EA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [Util] Warn and Remove Invalid GUCs (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: [Util] Warn and Remove Invalid GUCs
|
| Список | pgsql-hackers |
On Thu, May 22, 2025 at 9:00 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
Srinath Reddy Sadipiralla <srinath2133@gmail.com> writes:
> the extension is loaded and then i entered the bogus extension GUC into
> postgresql.conf and restarted, i did not observe any complain/warning .
Were you looking in the right place? I experimented with adding
shared_preload_libraries = 'plpgsql' # (change requires restart)
plpgsql.bogus = 1
to postgresql.conf. Restarting the server, I see in the
postmaster log:
2025-05-22 11:16:45.724 EDT [1526138] WARNING: invalid configuration parameter name "plpgsql.bogus", removing it
2025-05-22 11:16:45.724 EDT [1526138] DETAIL: "plpgsql" is now a reserved prefix.
2025-05-22 11:16:45.728 EDT [1526138] LOG: starting PostgreSQL 18beta1 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-26), 64-bit
... etc etc ...
Tom, the problem is when the prefix is a typo ,my bad i should have specified as bogus prefix instead of bogus GUC ,can you please try again with
"lpgsql.bogus = 1" .
В списке pgsql-hackers по дате отправления: