On Sat, Jul 18, 2020 at 6:31 PM Chapman Flack wrote:
>
> On 07/18/20 05:46, Amit Kapila wrote:
> > I don't think so. I think you can use 'pg_ctl start' to achieve that.
> > I think the JOBS stuff is primarily required when we use 'register'
> > operation (aka runs server via service). For example
On 7/18/20 5:46 AM, Amit Kapila wrote:
>
>> I don't have an especially easy way to experiment on Windows; I can push
>> experiments to the CI service and wait a bit to see what they do, but
>> I figured I'd ask here first.
>>
> I have tried and 'pg_ctl stuff seems to be working for a privileged
>
On 07/18/20 05:46, Amit Kapila wrote:
> I don't think so. I think you can use 'pg_ctl start' to achieve that.
> I think the JOBS stuff is primarily required when we use 'register'
> operation (aka runs server via service). For example, if you see one
> of the Job options "JOB_OBJECT_LIMIT_DIE_ON_U
On Sat, Jul 18, 2020 at 5:33 AM Chapman Flack wrote:
>
> But there's a NOTE! in the comment for CreateRestrictedProcess: "Job object
> will only work when running as a service, because it's automatically
> destroyed when pg_ctl exits."
>
> I haven't been able to find any documentation of what that
Hi,
So, I am not a Windows native, and here I am mentoring a GSoC student
setting up CI on multiple environments, including Windows.
In my own development and testing, by habit I do everything from
unprivileged accounts, just spinning up an instance in a temp location,
running some tests, and shu
