Re: pgsql: Use data directory inode number, not port, to select SysV resour - Mailing list pgsql-committers

From Tom Lane
Subject Re: pgsql: Use data directory inode number, not port, to select SysV resour
Date
Msg-id 19250.1567784113@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgsql: Use data directory inode number, not port, to select SysVresour  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
Responses Re: pgsql: Use data directory inode number, not port, to select SysVresour
List pgsql-committers
Andrew Dunstan <andrew.dunstan@2ndquadrant.com> writes:
> On 9/5/19 1:32 PM, Tom Lane wrote:
>> Use data directory inode number, not port, to select SysV resource keys.

> This has caused the 017_shm.pl tests to be skipped on jacana and
> bowerbird, and to fail completely on my msys2 test system where the Perl
> has the relevant IPC:: modules, unlike the buildfarm animals.

I intended 017_shm.pl to be skipped on Windows builds; it's not apparent
to me that that script tests anything useful when we're not using SysV
shared memory.

I don't quite understand what the msys2 platform might be doing with
these IPC modules.  Do they actually do anything, or just fail at
runtime?  If the latter, maybe we can add something to the eval{}
block to check for present-but-doesnt-work?

            regards, tom lane



pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pgsql: Doc: remove some long-obsolete information from installation.sgm
Next
From: Tom Lane
Date:
Subject: pgsql: Doc: tweak installation doc edits made by commit 76c2af926.