Re: pgsql: Use data directory inode number, not port, to select SysVresour

Поиск
Список
Период
Сортировка
От Andrew Dunstan
Тема Re: pgsql: Use data directory inode number, not port, to select SysVresour
Дата
Msg-id a1c40fab-a38c-cb42-6879-125f834e837b@2ndQuadrant.com
обсуждение исходный текст
Ответы Re: pgsql: Use data directory inode number, not port, to select SysV resour  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: pgsql: Use data directory inode number, not port, to select SysVresour  (Noah Misch <noah@leadboat.com>)
Список pgsql-hackers
On 9/6/19 3:51 PM, Andrew Dunstan wrote:
> On 9/6/19 2:42 PM, Tom Lane wrote:
>> Andrew Dunstan <andrew.dunstan@2ndquadrant.com> writes:
>>> Given your stated intention, I think the simplest way to get it is just
>>> this, without worrying about what the perl modules might do:
>>> -if ($@)
>>> +if ($@ || $windows_os)
>> WFM, do you want to push that?
>>
>>             
>
> done.
>
>

[redirected to -hackers]


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.


cheers


andrew




В списке pgsql-hackers по дате отправления:

Предыдущее
От: Andrew Dunstan
Дата:
Сообщение: Re: MSVC buildfarm critters are not running modules' TAP tests
Следующее
От: Tom Lane
Дата:
Сообщение: Re: MSVC buildfarm critters are not running modules' TAP tests