From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Ian Lawrence Barwick <barwick(at)gmail(dot)com> |
Cc: | Matthias Apitz <guru(at)unixarea(dot)de>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: mystery with postgresql.auto.conf |
Date: | 2024-04-10 14:33:50 |
Message-ID: | af3195aec84020b8e38cf7b3c20d047ef9a7c477.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, 2024-04-10 at 10:26 -0400, Tom Lane wrote:
> Ian Lawrence Barwick <barwick(at)gmail(dot)com> writes:
> > 2024年4月10日(水) 21:40 Matthias Apitz <guru(at)unixarea(dot)de>:
> > > Why it does not give an error because the shared lib isn't there?
>
> > ALTER SYSTEM is a way of modifying the PostgreSQL configuration file
> > via SQL; just as when you modify it manually, changes are not applied
> > until you actually reload the configuration.
> > See: https://www.postgresql.org/docs/current/sql-altersystem.html
>
> Even if you had issued a reload, you would not have noticed the
> faulty setting without looking into the postmaster's log for
> warning messages. The system wouldn't get in your face about it
> until you did a postmaster restart.
An alternative to looking at the log file is to
SELECT * FROM pg_file_settings WHERE error IS NOT NULL;
after you reload.
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | Dominique Devienne | 2024-04-10 14:48:42 | Re: Some advice need after a 20 year gap after Ingres/GUIs |
Previous Message | Tom Lane | 2024-04-10 14:26:05 | Re: mystery with postgresql.auto.conf |