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 1qu5Ux-00GCL2-GT for pgsql-bugs@arkaria.postgresql.org; Sat, 21 Oct 2023 06:30:11 +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 1qu5Uu-00EYzB-Ni for pgsql-bugs@arkaria.postgresql.org; Sat, 21 Oct 2023 06:30:09 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qu5Uu-00EYx8-8Z for pgsql-bugs@lists.postgresql.org; Sat, 21 Oct 2023 06:30:09 +0000 Received: from mail-lf1-x12b.google.com ([2a00:1450:4864:20::12b]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qu5Ur-001YBr-Lx for pgsql-bugs@lists.postgresql.org; Sat, 21 Oct 2023 06:30:07 +0000 Received: by mail-lf1-x12b.google.com with SMTP id 2adb3069b0e04-5046bf37ec1so2013684e87.1 for ; Fri, 20 Oct 2023 23:30:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1697869803; x=1698474603; darn=lists.postgresql.org; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=R2F24hITnIxI0+dHwu9/l8Onlo5X5CMukeEpt2Q7e+A=; b=QvHqcUrUVQgNo4+o4530Qj+nJQJYcE5lGVwykPG4tWmbTDMauN3NjOdx7X0cBbUCuE NNnQLog9Y0PWIGVZDW8/R7/vkxu4bC59fWAVis2cRCUMP8pCuZdO/hOX+HRtAE6PdFpq xqv9FNhE/+W1hrSVYnu6e8xTn5Sth7CtrM5UtXoc+lUjJzt8/l4DmQuVmxS6qEjFcEcf semr/IBZs317/uyYf0dykIzG9N4ORLkzEHRoc9JGnlsD96+lS+6OXIF1fioQsFvC/CZH h0AxtFAyCAoo9nbt1Ou8LU5ruOqn9ursYV/OM2S/FThs9MKAGVq46c44QaOdRn87k+2K VbVw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1697869803; x=1698474603; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=R2F24hITnIxI0+dHwu9/l8Onlo5X5CMukeEpt2Q7e+A=; b=u3Lts+6MGQl8okb3dUIhBa9US/Dh6ZQL3l2bw69m5NsiEeTIUpzU7HBJFInmws+brO 6QAUDvzX70iNS8RYbOBlX7XcgBYTfAKjHH0quSkZzl7eniv8vCqvjl4VPzqD71vGdw5u Eu5lMvumWiZyv664FvVeHnSZQ834afK15nJTArK6lApzFTaBKNMMKgfuYPziN9G5Z/vE vWeC8An1RJp58x5RtThvPX7PxRDpNR3MV9Rxnd+AWTvyHBj/Vic+oWcoEOM3ZVnbCaPy NxGu+extobQrcVKM1/jC8eCiKla6kvWbhPujgTC+/urOwC5lUEitaqKHQig384/CmV3g qHJg== X-Gm-Message-State: AOJu0Yx6iq4WUlWwDiv+uxNPmPfwxbJZT9BLIkLy37NBBt5TFZDamFWa o2HtiwM5l6iGMi3p76/iByo= X-Google-Smtp-Source: AGHT+IFBc6hvVoRkLH0/fZ9UatvIFi719cENfelk43fT0oSMmgNl/oWJv5zEK20+K1gLVv9A5dQmMw== X-Received: by 2002:a05:6512:348d:b0:507:9b4a:21bf with SMTP id v13-20020a056512348d00b005079b4a21bfmr2928460lfr.45.1697869802738; Fri, 20 Oct 2023 23:30:02 -0700 (PDT) Received: from [1.0.0.7] ([178.155.28.40]) by smtp.gmail.com with ESMTPSA id n17-20020a05651203f100b00500829f7b2bsm714147lfq.250.2023.10.20.23.30.01 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 20 Oct 2023 23:30:02 -0700 (PDT) Message-ID: Date: Sat, 21 Oct 2023 09:30:00 +0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Subject: Re: BUG #18165: Could not duplicate handle for "Global/PostgreSQL.xxxxxxxxxx": Bad file descriptor Content-Language: en-US To: Thomas Munro , Tom Lane Cc: Andres Freund , maxime.boyer@cra-arc.gc.ca, pgsql-bugs@lists.postgresql.org References: <18165-bf4f525cea6e51de@postgresql.org> <3998077.1697840164@sss.pgh.pa.us> <20231020225433.yhcw4qjbeixpgglh@awork3.anarazel.de> <4019765.1697851177@sss.pgh.pa.us> From: Alexander Lakhin In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi Thomas, 21.10.2023 08:26, Thomas Munro wrote: > And concretely this would be the fix, I think. But I don't have > Windows, and for reasons I haven't fathomed I haven't yet managed to > reproduce it by pushing a change of default min_dynamic_shared_memory > to CI. Is there any chance that a Postgres hacker on Windows could > confirm the above theory, and that the attached fixes it? I've tried on master: echo min_dynamic_shared_memory = 10MB >c:\temp\extra.config set TEMP_CONFIG=c:\temp\extra.config vcregress check and got: ... Installation complete. # initializing database system by running initdb # postmaster failed, examine ".../src/test/regress/log/postmaster.log" for the reasonBail out! >cat ../../../src/test/regress/log/postmaster.log 2023-10-20 23:12:46.110 PDT postmaster[3140] LOG:  starting PostgreSQL 17devel, compiled by Visual C++ build 1928, 64-bit 2023-10-20 23:12:46.113 PDT postmaster[3140] LOG:  listening on IPv6 address "::1", port 55312 2023-10-20 23:12:46.113 PDT postmaster[3140] LOG:  listening on IPv4 address "127.0.0.1", port 55312 2023-10-20 23:12:46.129 PDT startup[6188] LOG:  database system was shut down at 2023-10-20 23:12:41 PDT 2023-10-20 23:12:46.130 PDT startup[6188] FATAL:  could not duplicate handle for "Global/PostgreSQL.753594369": Bad file descriptor 2023-10-20 23:12:46.132 PDT postmaster[3140] LOG:  startup process (PID 6188) exited with exit code 1 2023-10-20 23:12:46.132 PDT postmaster[3140] LOG:  aborting startup due to startup process failure 2023-10-20 23:12:46.132 PDT postmaster[3140] LOG:  database system is shut down With your patch applied, `vcregress check` passes just fine. Best regards, Alexander