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 1sfaqc-008AYu-7O for pgsql-hackers@arkaria.postgresql.org; Sun, 18 Aug 2024 08:01:10 +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 1sfapZ-0081f3-Qq for pgsql-hackers@arkaria.postgresql.org; Sun, 18 Aug 2024 08:00:06 +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 1sfapZ-0081ee-Ez for pgsql-hackers@lists.postgresql.org; Sun, 18 Aug 2024 08:00:06 +0000 Received: from mail-lj1-x22d.google.com ([2a00:1450:4864:20::22d]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sfapW-000FQj-HA for pgsql-hackers@postgresql.org; Sun, 18 Aug 2024 08:00:05 +0000 Received: by mail-lj1-x22d.google.com with SMTP id 38308e7fff4ca-2f3b7aba3dbso40683461fa.3 for ; Sun, 18 Aug 2024 01:00:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1723968002; x=1724572802; darn=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=7RTBUOGSCCiynvb5oMRH/ZRwuMcKSUeVbMchu515ChU=; b=dqjQteKQ+OPHROTRnWrBBgt1yaalB6IaGQhzqBaHguHHRHBPIDbPOqHMny6uUOJQoR JUQruhUaBaEF5j59DtvhH/YYtQ1yj+qUIbmVNOWz7KvQlKcPrtG3xj0M1cp0Sw58tuAk EXSLojgwfJ1vVilKE9PgVMSknzC4RgGqQhqsrMZ1NtxXJ7VPwdSmEHGou5NMQBt/3hZf A9bYohhv+gz3bGfpcr+2jktj/CuvJVhjKYQI2NZSljfzQ9pAsRXvTkUOWxDmCcD9uE51 nT6IcwdP+bSzxAu4ZBYevwyWhI8lD6bfJGWL0T3rUxezg2Hz+93Zv/rliVJyYJ9t2hr7 7Rkg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1723968002; x=1724572802; 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=7RTBUOGSCCiynvb5oMRH/ZRwuMcKSUeVbMchu515ChU=; b=DKxVBaoB2c6Q60xGs79VFcf3SA+4RNkDInd0oKv4v2BiSauxmV91dLUFoeidm9H31J MiZnb3vaD74EyGFc05lgUoMil+OUVqSmsdhjtXatbJBAdGRhNkLMvU33QbLzq5OvrGC6 a9NnyFwkx6yzp3kam1hWN38N3ZIpSFajMNBIKRyauorUYa7WNhDGjQ60+MZwTV1zTymd 0omw0VwN4J+KoRUyUMBt7xf4xNRU+M5qJfSSzdeH5n4BVuu5wMTmFGgXAFI88JkxQAbM neUa1A+xA6Z5/770ex/gRrOJnLKnnYc9/E+QGt0f5y1NFVHr4CdxwVnFe2TVuO79ZuTQ zM3w== X-Gm-Message-State: AOJu0Yw86DUdCKXd2AfNpdYBORkQmWXplVr0KUHHvkuFAuI5xaYsYg/t KHHN1+sKa3RavGUtMuTIx+04XcpOhCiCxobVYbFaZ2qV8yBI0CXG X-Google-Smtp-Source: AGHT+IEUbhc9ojCP2Itz/KH88JL3GCUrfw0m7A5jC0aR8tXBR8IuvjcwnPivVGnYeBVkuUWuPuwB9g== X-Received: by 2002:a05:651c:b10:b0:2ef:2e6b:4105 with SMTP id 38308e7fff4ca-2f3be5f7568mr58933201fa.34.1723968001611; Sun, 18 Aug 2024 01:00:01 -0700 (PDT) Received: from [1.0.0.7] ([178.155.25.122]) by smtp.gmail.com with ESMTPSA id 38308e7fff4ca-2f3b771ece8sm11208671fa.118.2024.08.18.01.00.00 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 18 Aug 2024 01:00:01 -0700 (PDT) Message-ID: <451b0797-83b8-cdbc-727f-8d7a7b0e3bca@gmail.com> Date: Sun, 18 Aug 2024 11:00: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: Refactoring postmaster's code to cleanup after child exit Content-Language: en-US To: Heikki Linnakangas , Thomas Munro Cc: "pgsql-hackers@postgresql.org" References: <835232c0-a5f7-4f20-b95b-5b56ba57d741@iki.fi> <8f2118b9-79e3-4af7-b2c9-bd5818193ca4@iki.fi> 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 Hello Heikki, 10.08.2024 00:13, Heikki Linnakangas wrote: > > Committed the patches up to and including this one, with tiny comment changes. I've noticed that on the current HEAD server.log contains binary data (an invalid process name) after a child crash. For example, while playing with -ftapv, I've got: SELECT to_date('2024 613566758 1', 'IYYY IW ID'); server closed the connection unexpectedly grep -a 'was terminated' server.log 2024-08-18 07:07:06.482 UTC|||66c19d96.3482f6|LOG:  `�!x� (PID 3441407) was terminated by signal 6: Aborted It looks like this was introduced by commit 28a520c0b (IIUC, namebuf in CleanupBackend() may stay uninitialized in some code paths). Best regards, Alexander