AW: BUG #15641: Autoprewarm worker fails to start on Windows with huge pages in use Old PostgreSQL community/pgsql-bugs x

Hans Buschmann <buschmann@nidsa.net>

From: "Hans Buschmann" <buschmann@nidsa.net>

To: "Mithun Cy" <mithun.cy@gmail.com>

Cc: "Mithun Cy" <mithun.cy@enterprisedb.com>, <thomas.munro@gmail.com>, <pgsql-bugs@lists.postgresql.org>, "Robert Haas" <robertmhaas@gmail.com>

Date: 2019-02-25T10:59:48Z

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


Glad to hear you could reproduce the case easily.

I wanted to add that the problem as it seems now should'nt be restricted to Windows only.

Another thing is the semantic scope of pg_prewarm:

Prewarming affects the whole cluster, so at instance start we can meet some active and/or some dropped databases.

To not affect the other databases the prewarming should occur on all non dropped databases and omit only the dropped ones.

Hope your thinking gives a good patch... ;)

Hans Buschmann