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 1w8G4Y-000M8B-2f for pgsql-bugs@arkaria.postgresql.org; Thu, 02 Apr 2026 11:18:51 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1w8G4X-005QyT-21 for pgsql-bugs@arkaria.postgresql.org; Thu, 02 Apr 2026 11:18:50 +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.96) (envelope-from ) id 1w8G4X-005QyL-0f for pgsql-bugs@lists.postgresql.org; Thu, 02 Apr 2026 11:18:49 +0000 Received: from forwardcorp1d.mail.yandex.net ([2a02:6b8:c41:1300:1:45:d181:df01]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1w8G4U-00000000Ajf-1LyZ for pgsql-bugs@lists.postgresql.org; Thu, 02 Apr 2026 11:18:48 +0000 Received: from mail-nwsmtp-smtp-corp-main-68.klg.yp-c.yandex.net (mail-nwsmtp-smtp-corp-main-68.klg.yp-c.yandex.net [IPv6:2a02:6b8:c42:94a9:0:640:a3fa:0]) by forwardcorp1d.mail.yandex.net (Yandex) with ESMTPS id 992ED80784; Thu, 02 Apr 2026 14:18:41 +0300 (MSK) Received: from smtpclient.apple (unknown [2a02:6bf:8080:8d::1:2e]) by mail-nwsmtp-smtp-corp-main-68.klg.yp-c.yandex.net (smtpcorp/Yandex) with ESMTPSA id eIaVYF0MlqM0-0m6gcKc3; Thu, 02 Apr 2026 14:18:41 +0300 X-Yandex-Fwd: 1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex-team.ru; s=default; t=1775128721; bh=3oeLRlhjo4rPcAew9S0cTYEmeGtAI6lth9Kx0p1Qg2E=; h=Message-Id:To:Date:References:Cc:In-Reply-To:From:Subject; b=ukNIX76KgLK/ZwamQ43WutPUFyX4llxgHbUgj5Pg0S21AxFoMNdAcdciSEhzSDXwK 3xkWhZAsCQ7mgawtP8ILZJmBt0pozfhmtKUsIgXphGb/1YLpmCqarMaFTrt8pWlrVE I2MBHbksBmKmdLJK0BgBm0Gilr0LqlZ+WFWhRyJQ= Authentication-Results: mail-nwsmtp-smtp-corp-main-68.klg.yp-c.yandex.net; dkim=pass header.i=@yandex-team.ru Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.400.21\)) Subject: Re: BUG #19382: Server crash at __nss_database_lookup From: Andrey Borodin In-Reply-To: Date: Thu, 2 Apr 2026 16:18:29 +0500 Cc: songjinzhou , dllggyx , pgsql-bugs Content-Transfer-Encoding: quoted-printable Message-Id: References: <19382-4c2060ffee72759b@postgresql.org> To: surya poondla X-Mailer: Apple Mail (2.3864.400.21) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi! Thanks for working on this! > On 20 Mar 2026, at 23:16, surya poondla = wrote: >=20 > I'll post an updated patch with this improvement. After your patch Postgres still crashes on this test: CREATE TYPE foo AS (a INT, b INT); BEGIN; DECLARE c CURSOR FOR SELECT (i, power(2, 30))::foo FROM = generate_series(1,10) i; FETCH c; ALTER TYPE foo ALTER ATTRIBUTE b TYPE TEXT; FETCH c; COMMIT; This test case was proposed in this thread, but I suggest treating this = as a separate bug needing separate fix. In my opinion in both cases (PL/pgSQL + CURSOR) we should error out = instead of trying to remediate type changes. Best regards, Andrey Borodin.=