| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Aditya Toshniwal <aditya(dot)toshniwal(at)enterprisedb(dot)com> |
| Cc: | Pravesh Sharma <pravesh(dot)sharma(at)enterprisedb(dot)com>, pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | Re: Require suggestions on feature 6794 |
| Date: | 2024-11-26 11:33:56 |
| Message-ID: | CA+OCxoyNEXsXQexNJjn=5F4yaaQ1_Cfh4sm9agCH=H4EwandaA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
On Tue, 26 Nov 2024 at 11:30, Aditya Toshniwal <
aditya(dot)toshniwal(at)enterprisedb(dot)com> wrote:
> Hi Pravesh,
>
> In addition to that, why do we need env vars at all? We can simply pass
> them as arguments to passexec script. It's up to the users to use it or
> ignore it.
>
Or do some string substitution in the command, e.g.
/path/to/passexec.sh $HOST$ $PORT$
or similar, so the user has even more flexibility. I know that is done in
PEM in a few places, possibly in pgAdmin too, though I don't recall offhand
(if it is, we should be consistent on how the parameters are notated).
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
pgEdge: https://www.pgedge.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rohit Bhati | 2024-11-27 07:11:59 | Re: Require suggestion for issue #6513 |
| Previous Message | Aditya Toshniwal | 2024-11-26 11:29:47 | Re: Require suggestions on feature 6794 |