From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Wilm Hoyer <W(dot)Hoyer(at)dental-vision(dot)de>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #17448: In Windows 10, version 1703 and later, huge_pages doesn't work. |
Date: | 2022-04-27 16:48:41 |
Message-ID: | 20220427164841.xcpdcmq76ixn7zgx@jrouhaud |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs Postg젠 토토SQL : |
On Wed, Apr 27, 2022 at 05:13:12PM +0900, Michael Paquier wrote:
> On Tue, Apr 26, 2022 at 12:54:35PM +0800, Julien Rouhaud wrote:
> > so I'm still on the opinion that we should
> > unconditionally use the FILE_MAP_LARGE_PAGES flag if it's defined and call it a
> > day.
>
> Are we sure that this is not going to cause failures in environments
> where the flag is not supported?
I don't know for sure as I have no way to test, but it would be very lame for
an OS to provide a #define explicitly intended for one use case if that use
case can't handle that flag yet.
From | Date | Subject | |
---|---|---|---|
Next Message | Julien Rouhaud | 2022-04-27 16:52:28 | Re: BUG #17448: In Windows 10, version 1703 and later, huge_pages doesn't work. |
Previous Message | Loïc Revest | 2022-04-27 15:19:30 | Re: lag() default value ignored for some window partition depending on table records count? |
From | Date | Subject | |
---|---|---|---|
Next Message | Julien Rouhaud | 2022-04-27 16:52:28 | Re: BUG #17448: In Windows 10, version 1703 and later, huge_pages doesn't work. |
Previous Message | Tom Lane | 2022-04-27 16:45:14 | Unstable tests for recovery conflict handling |