Re: BUG #18971: Server passes an invalid (indirect) path in PGDATA to the external program

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Dmitry Kovalenko <d(dot)kovalenko(at)postgrespro(dot)ru>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18971: Server passes an invalid (indirect) path in PGDATA to the external program
Date: 2025-06-28 20:19:13
Message-ID: 2341065.1751141953@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Dmitry Kovalenko <d(dot)kovalenko(at)postgrespro(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David G. Johnston 2025-06-28 21:12:02 Re: BUG #18971: Server passes an invalid (indirect) path in PGDATA to the external program
Previous Message Dmitry Kovalenko 2025-06-28 19:32:59 Re: BUG #18971: Server passes an invalid (indirect) path in PGDATA to the external program