From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | Thomas Kellerer <shammat(at)gmx(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Official Windows Installer and Documentation |
Date: | 2022-07-28 02:17:49 |
Message-ID: | 20220728021749.da5xyrh7xbt6qm2c@jrouhaud |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jul 27, 2022 at 07:02:51PM -0700, David G. Johnston wrote:
>
> In the end the problem is ours and cannot be simply assigned to a
> third-party. So let's resolve it here (on this list, whatever the
> solution) where representatives from all parties are present.
We could amend the pg_upgrade (and maybe other if needed, but I don't see any
other occurences of RUNAS) documentation to be a bit more general, like the
non-windows part of it, maybe something like
For Windows users, you must be logged into an administrative account, and then
start a shell as the user running the postgres service and set the proper path.
Assuming a user named postgres and the binaries installed in C:\Program
Files\PostgreSQL\14:
RUNAS /USER:postgres "CMD.EXE"
SET PATH=%PATH%;C:\Program Files\PostgreSQL\14\bin;
It's ultimately up to the users to adapt the commands to match their
environment.
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2022-07-28 02:31:35 | Re: Official Windows Installer and Documentation |
Previous Message | Thomas Munro | 2022-07-28 02:12:13 | Re: fairywren hung in pg_basebackup tests |