Re: pg_regress: lookup shellprog in $PATH

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Gurjeet Singh <gurjeet(at)singh(dot)im>, Postgres Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_regress: lookup shellprog in $PATH
Date: 2022-08-25 15:04:35
Message-ID: CA+Tgmoa7+X=sO_0jJkzO7RvEnA_C4hj_zV79yxMYdaSERf0eXQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Aug 25, 2022 at 10:48 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> If we were executing a program that the user needs to have some control
> over, sure, but what we have here is an implementation detail that I
> doubt anyone cares about. The fact that we're using a shell at all is
> only because nobody has cared to manually implement I/O redirection logic
> in these places; otherwise we'd be execl()'ing the server or psql directly.
> Maybe the best answer would be to do that, and get out of the business
> of knowing where the shell is?

Well that also would not be crazy.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christoph Berg 2022-08-25 15:13:06 Re: pg_receivewal and SIGTERM
Previous Message David Rowley 2022-08-25 14:56:15 Re: shadow variables - pg15 edition