Re: pgsql: Use data directory inode number, not port, to select SysVresour - Mailing list pgsql-hackers

From Noah Misch
Subject Re: pgsql: Use data directory inode number, not port, to select SysVresour
Date
Msg-id 20190913062028.GA3458481@rfd.leadboat.com
Whole thread Raw
In response to Re: pgsql: Use data directory inode number, not port, to select SysVresour  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
List pgsql-hackers
On Sun, Sep 08, 2019 at 05:54:12PM -0400, Andrew Dunstan wrote:
> I'm going to disable this test (src/test/recovery/t/017_shm.pl) on
> Windows on the back branches too unless there's a violent objection. The
> reason is that the script runs "postgres --single" and that fails on
> Windows when run by an administrative account. We've carefully enabled
> postgres and its tests to run safely under an admin account. I
> discovered this as part of my myss2 testing.

I'm reading that the test falsified this assertion that we've enabled postgres
to run safely under an admin account.  Enabling safe use of admin accounts
entails fixing single-user mode.  (Alternately, one could replace the "vacuum
that database in single-user mode" errhint with a reference to some
not-yet-built alternative.  That sounds harder.)



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [HACKERS] [PATCH] pageinspect function to decode infomasks
Next
From: Amit Kapila
Date:
Subject: Re: pgbench - allow to create partitioned tables