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 1s6aP5-000WYx-5u for pgsql-general@arkaria.postgresql.org; Mon, 13 May 2024 18:28:04 +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 1s6aP5-0048EV-52 for pgsql-general@arkaria.postgresql.org; Mon, 13 May 2024 18:28:03 +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 1s6aP4-0048EN-Qk for pgsql-general@lists.postgresql.org; Mon, 13 May 2024 18:28:02 +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 1s6aP1-0003OK-E9 for pgsql-general@lists.postgresql.org; Mon, 13 May 2024 18:28:01 +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 44DIRvSK830072; Mon, 13 May 2024 14:27:57 -0400 From: Tom Lane To: Christophe Pettus cc: Adrian Klaver , "pgsql-generallists.postgresql.org" Subject: Re: UTC is not a time zone? In-reply-to: <8DA3DC1C-E406-4921-8A86-A83BF140E13D@thebuild.com> References: <327870A4-F35C-462C-9F64-E0838374AFDF@thebuild.com> <63e65356-9cb5-48b7-9bc5-5c734013ebe1@aklaver.com> <828310.1715624225@sss.pgh.pa.us> <8DA3DC1C-E406-4921-8A86-A83BF140E13D@thebuild.com> Comments: In-reply-to Christophe Pettus message dated "Mon, 13 May 2024 11:18:12 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <830070.1715624877.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Mon, 13 May 2024 14:27:57 -0400 Message-ID: <830071.1715624877@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Christophe Pettus writes: > On May 13, 2024, at 11:17, Tom Lane wrote: >> What's causing that I can't say. It doesn't look like we log the >> errno anywhere when failing to read a zone file :-( > File descriptor exhaustion? (Of course, that would mean something somew= here is leaking them, which is another problem.) Since this is in a pretty-new process, it would have to be global FD exhaustion, that is ENFILE not EMFILE. (Assuming macOS even has that concept; its BSD roots sure do, but who knows what Apple's done to it over the years.) You'd likely have seen more side-effects of such a condition. I was wondering more about permissions checks gone wrong, comparable to the antivirus-induced misbehaviors we hear about on Windows. Not that that's a comforting answer. regards, tom lane