Possible regression from PG10 to PG11 on windows - Mailing list pgsql-bugs

From Paul van der Linden
Subject Possible regression from PG10 to PG11 on windows
Date
Msg-id AM0PR0402MB3425DD01DC0DF74C770E3A5DEC660@AM0PR0402MB3425.eurprd04.prod.outlook.com
Whole thread Raw
List pgsql-bugs
Hi,

I have a suspicion that since the upgrade of Postgres to 11 processes are not fully closed after their job is done.
The symptom I noticed IS that the process-ids are steadily increasing for new proccesses, they used to be in the
4-digitnumbers with older Postgres versions, and now they are in the 6-digit range and still increasing. 

It doesn't seem to have any other effects than that, but in theory it could run out of resources of some kind given
enoughtime. 

A possible cause of this could be that a handle to a finished backend-process isn't closed, and thus still hold a
referenceto that process (and prevent reuse of it's process-id). 

Didn't investigate deeper yet, but perhaps this triggers someone's mind enough to know the cause/solution?

Paul

pgsql-bugs by date:

Previous
From: Andrew Gierth
Date:
Subject: Re: BUG #15634: extension missing
Next
From: Michael Paquier
Date:
Subject: Re: BUG #15631: Generated as identity field in a temporary tablewith on commit drop corrupts system catalogs