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 1vxMsd-00AaVz-2j for pgsql-bugs@arkaria.postgresql.org; Tue, 03 Mar 2026 10:21:32 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vxMsb-006GKB-3D for pgsql-bugs@arkaria.postgresql.org; Tue, 03 Mar 2026 10:21:30 +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 1vxKAt-005Bk7-03 for pgsql-bugs@lists.postgresql.org; Tue, 03 Mar 2026 07:28:11 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1vxKAn-000000008zV-3sM7 for pgsql-bugs@lists.postgresql.org; Tue, 03 Mar 2026 07:28:11 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:Cc:From:To:Subject: Content-Transfer-Encoding:MIME-Version:Content-Type:Sender:Content-ID: Content-Description:In-Reply-To:References; bh=sFjib25t4sbyhWEfaLtq7JXVAYWp5YdPhBorKaA84GY=; b=MgTb4TMdszYE3P2AjUInGCBtE6 PPndqCu9xZ7BeB6/6zEoHwekZR/PAmMut9udIda+Ialbpb+WlIJCkO4jyyPSqfBCrBoLUDJCCTF9w Mgxb+mOb/xI2uqfvAie6mohZPq4gwm4GYbxqLfTGr0J1CJDo+k3KmoC55YDbXkLEkY9y/HWFipzAk Ap6bcVnXQXri74L2gP9l/DS276o1mp11tmDOoRGwIt9Fkdp026EqUeBhwbQcURjiYPdarkCw01igB j2Cz9890ugEhwpbnThvAdU+nABzG55ofVj99BHTlx+NovbvepjdLrqY56iTpFqrodi850cjJ8m0j7 HMs3qrMQ==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vxKAm-006CYq-0f for pgsql-bugs@lists.postgresql.org; Tue, 03 Mar 2026 07:28:05 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vxKAj-000ipI-2y for pgsql-bugs@lists.postgresql.org; Tue, 03 Mar 2026 07:28:03 +0000 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: BUG #19423: canonicalize_path does not function correctly when processing paths that contain . and .. To: pgsql-bugs@lists.postgresql.org From: PG Bug reporting form Cc: 1003931418@qq.com Reply-To: 1003931418@qq.com, pgsql-bugs@lists.postgresql.org Date: Tue, 03 Mar 2026 07:27:44 +0000 Message-ID: <19423-a45c4524977e1704@postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk The following bug has been logged on the website: Bug reference: 19423 Logged by: SHIQI LI Email address: 1003931418@qq.com PostgreSQL version: 14.22 Operating system: linux Description: =20 When the input parameter path of the function is /tmp/root_hack4_test_tablespace/./../../test, the expected result after processing by canonicalize_path is /test, but the actual result remains /tmp/root_hack4_test_tablespace/./../../test. The implementation of this function differs significantly between version 14, version 15, and later versions.