Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ruYtv-0068MK-Vh for pgsql-general@arkaria.postgresql.org; Wed, 10 Apr 2024 14:26:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1ruYtu-003KvE-QI for pgsql-general@arkaria.postgresql.org; Wed, 10 Apr 2024 14:26:10 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ruYtu-003Kv5-Fq for pgsql-general@lists.postgresql.org; Wed, 10 Apr 2024 14:26:10 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ruYtr-000Cz0-Md for pgsql-general@lists.postgresql.org; Wed, 10 Apr 2024 14:26:09 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 43AEQ51T4020597; Wed, 10 Apr 2024 10:26:05 -0400 From: Tom Lane To: Ian Lawrence Barwick cc: Matthias Apitz , pgsql-general@lists.postgresql.org Subject: Re: mystery with postgresql.auto.conf In-reply-to: References: Comments: In-reply-to Ian Lawrence Barwick message dated "Wed, 10 Apr 2024 21:49:49 +0900" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <4020595.1712759165.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Wed, 10 Apr 2024 10:26:05 -0400 Message-ID: <4020596.1712759165@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Ian Lawrence Barwick writes: > 2024年4月10日(水) 21:40 Matthias Apitz : >> 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. regards, tom lane