| From: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
|---|---|
| To: | "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Supporting huge pages on Windows |
| Date: | 2017-03-08 10:17:59 |
| Message-ID: | CAEepm=0miZO1QHBRXjGvy==coO9rc=gjXrK34ZxR5qA8p0zSPg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Feb 23, 2017 at 8:29 PM, Tsunakawa, Takayuki
<tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> wrote:
> [win_large_pages_v8.patch]
+ 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>.
+ Huge pages are known as large pages on Windows. To use them,
you need to
+ To start the database server on the command prompt as a
standalone process,
+ not as a Windows service, run the command prompt as an administrator or
+ disable the User Access Control (UAC). When the UAC is
enabled, the normal
+ command prompt revokes the user right Lock Pages in Memory.
The line beginning 'Huge pages are known as...' has been accidentally
duplicated.
--
Thomas Munro
http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Gierth | 2017-03-08 10:30:21 | Re: Hash support for grouping sets |
| Previous Message | Amit Langote | 2017-03-08 10:09:36 | Re: dropping partitioned tables without CASCADE |