| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, okano(dot)naoki(at)jp(dot)fujitsu(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #17448: In Windows 10, version 1703 and later, huge_pages doesn't work. |
| Date: | 2022-09-16 14:29:38 |
| Message-ID: | 3677878.1663338578@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Michael Paquier <michael(at)paquier(dot)xyz> writes:
> So based on that I think that we could just apply and backpatch what
> you have here. This issue is much easier to reason about on HEAD
> where we just care about Win >= 10, and we've be rather careful with
> changes like that when it came to Windows. Any objections about doing
> a backpatch? I'd like to do so after an extra lookup, if there are no
> objections. Or would folks prefer a HEAD-only fix for now?
Let's just fix it in HEAD. I think the risk/reward ratio isn't very
good here.
(I'd be particularly against changing this in v10, because 10.23 will
be the last one; there will be no second chance if we ship it broken.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Francisco Olarte | 2022-09-16 14:33:07 | Re: BUG #17615: Getting error while inserting records in the table: invalid byte sequence for encoding "UTF8": 0xae |
| Previous Message | Michael Paquier | 2022-09-16 12:51:40 | Re: BUG #17448: In Windows 10, version 1703 and later, huge_pages doesn't work. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Julien Rouhaud | 2022-09-16 14:36:12 | Re: BUG #17448: In Windows 10, version 1703 and later, huge_pages doesn't work. |
| Previous Message | Tom Lane | 2022-09-16 14:26:29 | Re: Pruning never visible changes |