Re: [HACKERS] Supporting huge pages on Windows

Поиск
Список
Период
Сортировка
От Thomas Munro
Тема Re: [HACKERS] Supporting huge pages on Windows
Дата
Msg-id CAEepm=2Bv+098ED-nJd-5=oa5niMnbC_Hr1iuHr1ciDLvoXdTQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [HACKERS] Supporting huge pages on Windows  ("Tsunakawa, Takayuki" <tsunakawa.takay@jp.fujitsu.com>)
Ответы Re: [HACKERS] Supporting huge pages on Windows  ("Tsunakawa, Takayuki" <tsunakawa.takay@jp.fujitsu.com>)
Список pgsql-hackers
On Thu, Jan 5, 2017 at 4:12 PM, Tsunakawa, Takayuki
<tsunakawa.takay@jp.fujitsu.com> wrote:
> [win_large_pages_v4.patch]

Just a small suggestion about the wording in this patch:

+        This feature uses the large-page support on Windows. To use
the large-page
+        support, you need to assign Lock page in memory user right to
the Windows
+        user account which runs <productname>PostgreSQL</productname>.

In the Microsoft documentation I've seen, the privilege's name is
always written as "Lock Pages in Memory" (note: "Pages" plural, and
with initial capital letters).  It's quite hard to parse the sentence
otherwise!  How about this?
        Huge pages are known as large pages on Windows.  To use them,
you need to        assign the user right Lock Pages in Memory to the Windows user account        that runs
<productname>PostgreSQL</productname>.

+ ereport(elevel,
+ (errmsg("could not enable Lock pages in memory user right: error
code %lu", GetLastError()),
+ errdetail("Failed system call was OpenProcessToken.")));

Same comment about capitalisation of the privilege name in this and
other error messages.

-- 
Thomas Munro
http://www.enterprisedb.com



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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: [HACKERS] Re: [BUGS][PATCH] BUG #14486: Inserting and selecting interval have different constraints
Следующее
От: Tom Lane
Дата:
Сообщение: Re: [HACKERS] Group clear xid can leak semaphore count