Re: BUG #15641: Autoprewarm worker fails to start on Windows with huge pages in use Old PostgreSQL community/pgsql-bugs x
Mithun Cy <mithun.cy@gmail.com>
From: Mithun Cy <mithun.cy@gmail.com>
To: Mithun Cy <mithun.cy@enterprisedb.com>,
Hans Buschmann <buschmann@nidsa.net>, thomas.munro@gmail.com
Cc: pgsql-bugs@lists.postgresql.org, robertmhaas@gmail.com
Date: 2019-02-21T12:53:29Z
Lists: pgsql-bugs, pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Don't auto-restart per-database autoprewarm workers.
- fc8b39a46eb7 11.3 landed
- 1459e84cb2e5 12.0 landed
-
Fix race in dsm_attach() when handles are reused.
- 6c0fb9418925 12.0 cited
Hi Thomas, Hans, On Thu, Feb 21, 2019 at 2:16 PM Hans Buschmann <buschmann@nidsa.net> wrote: > > hello > > Since these are production systems, I did'nt set huge_pages=off. > (huge pages give performance, autoprewarm is not so necessary) I did turn autoprewarm on, windows server 2019 and postgresql 11.2 it runs fine even with huge_pages=on (Thanks to neha sharma). As Thomas said error is coming from per database worker and main worker waits till per data database worker exists so from code review I do see an issue of having an invalid handle in per database worker. A reproducible testcase will really help. I shall see to recheck the code again but I am not much hopeful without a proper testcase. -- Thanks and Regards Mithun Chicklore Yogendra EnterpriseDB: http://www.enterprisedb.com