From: | "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> |
---|---|
To: | 'Andres Freund' <andres(at)anarazel(dot)de> |
Cc: | 'Michael Paquier' <michael(dot)paquier(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com>, "Thomas Munro" <thomas(dot)munro(at)enterprisedb(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-04-04 06:06:42 |
Message-ID: | 0A3221C70F24FB45833433255569204D1F6BFE6F@G01JPEXMBYT05 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
From: pgsql-hackers-owner(at)postgresql(dot)org
> [mailto:pgsql-hackers-owner(at)postgresql(dot)org] On Behalf Of Andres Freund
> I don't think the errdetail is quite right - OpenProcessToken isn't really
> a syscall, is it? But then it's a common pattern already in wind32_shmem.c...
Yes, "Win32 API function" would be correct, but I followed the existing code...
> > + errdetail("Failed system call was %s.",
> > +"LookupPrivilegeValue")));
>
> Other places in the file actually log the arguments to the function...
The only place is CreateFileMapping. Other places (DuplicateHandle and MapViewOfFileEx) don't log arguments. I guess the original developer thought that size and name arguments to CreateFileMapping() might be useful for troubleshooting.
> Wonder if we should quote "Lock Pages in Memory" or add dashes, to make
> sure it's clear that that's the right?
I saw several Microsoft pages, including a page someone introduced me here, and they didn't quote the user right. I'm comfortable with the current code, but I don't mind if the committer adds some quotation.
> > + flProtect = PAGE_READWRITE | SEC_COMMIT |
> SEC_LARGE_PAGES;
>
> Why don't we just add the relevant flag, instead of overwriting the previous
> contents?
I don't have strong opinion on this...
> Uh - isn't that a behavioural change? Was this discussed?
Yes, I described this in the first mail. Magnus asked about this later and I replied.
Regards
Takayuki Tsunakawa
From | Date | Subject | |
---|---|---|---|
Next Message | Tsunakawa, Takayuki | 2017-04-04 06:18:04 | Re: Statement timeout behavior in extended queries |
Previous Message | Michael Paquier | 2017-04-04 06:02:30 | Letting the client choose the protocol to use during a SASL exchange |