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 <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1uVc19-002aKb-Jc
	for pgsql-bugs@arkaria.postgresql.org; Sat, 28 Jun 2025 20:19:19 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1uVc16-009Hp9-PI
	for pgsql-bugs@arkaria.postgresql.org; Sat, 28 Jun 2025 20:19:17 +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 <tgl@sss.pgh.pa.us>)
	id 1uVc16-009Hp0-Fb
	for pgsql-bugs@lists.postgresql.org; Sat, 28 Jun 2025 20:19:17 +0000
Received: from sss.pgh.pa.us ([68.162.161.243])
	by makus.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1uVc14-004UQO-31
	for pgsql-bugs@lists.postgresql.org;
	Sat, 28 Jun 2025 20:19:16 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 55SKJD4R2341066;
	Sat, 28 Jun 2025 16:19:13 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dmitry Kovalenko <d.kovalenko@postgrespro.ru>
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18971: Server passes an invalid (indirect) path in PGDATA to
 the external program
In-reply-to: <ec6c6594-8b0f-487d-a1e9-9f9f456bf573@postgrespro.ru>
References: <18971-53687392b125e4bf@postgresql.org>
 <2334360.1751138005@sss.pgh.pa.us>
 <ec6c6594-8b0f-487d-a1e9-9f9f456bf573@postgrespro.ru>
Comments: In-reply-to Dmitry Kovalenko <d.kovalenko@postgrespro.ru>
	message dated "Sat, 28 Jun 2025 22:32:59 +0300"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2341064.1751141953.1@sss.pgh.pa.us>
Date: Sat, 28 Jun 2025 16:19:13 -0400
Message-ID: <2341065.1751141953@sss.pgh.pa.us>
List-Id: <pgsql-bugs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-bugs@lists.postgresql.org>
List-Owner: <mailto:pgsql-bugs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-bugs>
Archived-At: 
 <https://www.postgresql.org/message-id/2341065.1751141953%40sss.pgh.pa.us>
Precedence: bulk

Dmitry Kovalenko <d.kovalenko@postgrespro.ru> writes:
> For my point of view, if you can't provider a valid path in PGDATA, do 
> not do it at all.

I'm not sure which part of "don't rely on PGDATA" you didn't get.
Under normal circumstances, Postgres itself doesn't set that at all.

If you want to establish a site convention that PGDATA is valid,
fine, but then it's on you to set it correctly.

			regards, tom lane