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.96) (envelope-from ) id 1vO39u-007d6E-0U for pgsql-hackers@arkaria.postgresql.org; Wed, 26 Nov 2025 00:13:22 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vO39s-00Cr8G-2O for pgsql-hackers@arkaria.postgresql.org; Wed, 26 Nov 2025 00:13:21 +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.96) (envelope-from ) id 1vO39s-00Cr88-1K for pgsql-hackers@lists.postgresql.org; Wed, 26 Nov 2025 00:13:20 +0000 Received: from mail-ej1-x633.google.com ([2a00:1450:4864:20::633]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vO39q-001Vpz-0v for pgsql-hackers@lists.postgresql.org; Wed, 26 Nov 2025 00:13:20 +0000 Received: by mail-ej1-x633.google.com with SMTP id a640c23a62f3a-b734fcbf1e3so1008342466b.3 for ; Tue, 25 Nov 2025 16:13:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1764115996; x=1764720796; darn=lists.postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=WSkorOsCshrGv8k8tDMRT65hn0HNM0qSROMdUgukDRU=; b=T7Yj3MhtGWiTSy6UiHqnaiC7Bohksnqujek1I+uLIcjHkDbHaFS9L8QioJ77ddnP1x KaV5E/LDWQGTmHA1wQn6vmYXDq168+Uet4+RoIkY033TcSuqWMFWTY9Hj90frYozdPnc 78qyfdhoXSImcNvvlv1HAduURuBxFQEp2bQIMp++bHY4oSZzTCyns/KJ9+5CHTgcnV4s a2TSz7sSZZDXvs83hURBIBintU6xVDdhh8rmKRGAe/eORFEOP6jeiTR3Tjz0XxHrERKl diXYoHleUC1kFw+0z86ztWephu3HDF/zAMndZGZgkV5lIojlff9tZZ0PvNjWAYD6CdWG YanA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1764115996; x=1764720796; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-gg:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=WSkorOsCshrGv8k8tDMRT65hn0HNM0qSROMdUgukDRU=; b=vGkY0sTno8PFyt/YRL5UwG+ySt1p5Ot/PeBwsnQCPoB/Gw/9drMT9/BzyFbIHG5Ys3 SzMekGogHKIsmhnots9XALUmD7SLCFwnL3SO2duZwemOaB03nwnNYCRP7atH+7EXBwVs 5IZuWKmJeTd6gKxuFUpJqMwIejHTWMPERwxZAfFg2hD0WUrIv5xKvWwaqfXX1osNSjgh kXNM7Yg7o7yaHemcS2pil4neY/T2VanAF2Ha1ocC4AyiBCi2G/2zB6h1+T6bJ9UbA3cb EM9HjMsePIFZWohIQKKQUr1hBglu+ZpLke6loNI3tQy4s2Bxm1nGpia2hrQLkGdJN3zb F6Vg== X-Gm-Message-State: AOJu0YwStR8UOj28dIC7Zro8aC6mKYsLkTKe718Q8nna6ZXueAFbRoad qY+0ncrhhOabEifz7LbceEfno/R3EDxlHJ0m6mwyByQEEBdLjYn7cWbIUeO/faWsIxqQnuN9AuO Olt4P9JRZHCPBHockPPYk9Gs1ZbB5vYeuTg== X-Gm-Gg: ASbGncsjmg5NphFhDkjUCIhYHyUH0GNsM/Mh41ClfKbbnoHVQOiRoskzraMTnCt/lMk ThMct4FpklYLSRcCFuebrsGDtzu13xbhnFRFGhmkM6ypdNa+BOgyDDJ7YRvBBVv+cfun5RluvOS Zkn80KqC2PyqxZ2iPJyl2Y+taKWqnWkw6SGyfCgpn0KXNY84qifd4YZFCM4mwsYUOqNb6FFdx5f uyeqaTXE6q4WjojkT7mjOLurPxtJWZmqLeabtVUe+unm1tFPsn+yHqFDehDQFzz9Mz7hSU7lA8Q YZ2HljC174ay2D3M3brRRksJEbI= X-Google-Smtp-Source: AGHT+IEYbm9AWGJm9xxIW90bPV4CxxKNdK+jMYaGxdyPl57qkGI3R7nBwec50P88RvXyBNbDYLphiKi6T2SYRLHoNOY= X-Received: by 2002:a17:907:94c9:b0:b72:9961:dc04 with SMTP id a640c23a62f3a-b7671703d94mr2075979766b.28.1764115996323; Tue, 25 Nov 2025 16:13:16 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Robert Haas Date: Tue, 25 Nov 2025 19:13:03 -0500 X-Gm-Features: AWmQ_bnYlvfXWNdYTHvmDTN2Vm9SEuV24LeC88694HuN2TOvxNSeOwGJ5F4oCek Message-ID: Subject: Re: pgsql: Teach DSM registry to ERROR if attaching to an uninitialized ent To: Nathan Bossart Cc: PostgreSQL Hackers Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, Nov 25, 2025 at 4:16=E2=80=AFPM Nathan Bossart wrote: > My tests seem happy, so I will plan on committing these patches tomorrow. > The only difference in v4 is that pg_get_dsm_registry_allocations() will = no > longer show partially-initialized entries. I thought that was the best > option in this case because such entries shouldn't have any allocated > memory, and retrying GetNamed*() would set *found to false. Without actually opening the new patch files, that seems OK to me. I think the important thing about such a view is that it shouldn't make any state changes; it should just show how things are. In my ideal world, it would probably show partially-initialized entires in some distinguishable way, like with a null size. But leaving them out is also defensible. The thing that I think really matters for failure cases is the ability to retry whatever's gone wrong, either to get it fixed or to see the error, and the other changes already accomplish that goal, so I'm happy. --=20 Robert Haas EDB: http://www.enterprisedb.com