| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Dmitry Kovalenko <d(dot)kovalenko(at)postgrespro(dot)ru>, 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 21:12:02 |
| Message-ID: | CAKFQuwbGC06vsmCXqs=OAwWd9CRjw7B0mkPbTCdSbdfLgDL6gQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Sat, Jun 28, 2025 at 1:19 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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 we have to tell someone to not rely on a value that we've set we've done
something wrong. Either haven't explained how to use it correctly, we've
set it in unusual circumstances when we should not have, or we are choosing
a bad value to set it in the first place. Setting it to an absolute path
would seem like the least problematic approach to take to make our system
more usable.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Anthony Hsu | 2025-06-28 23:37:13 | Re: BUG #18961: Race scenario where max_standby_streaming_delay is not honored |
| Previous Message | Tom Lane | 2025-06-28 20:19:13 | Re: BUG #18971: Server passes an invalid (indirect) path in PGDATA to the external program |