Re: PMChildFlags array

On 10/3/19 3:57 AM, bhargav kamineni wrote:
> Hi,
> 
> Observed below errors  in logfile
> 
> 2019-09-20 02:00:24.504 UTC,,,99779,,5d73303a.185c3,73,,2019-09-07 
> 04:21:14 UTC,,0,FATAL,XX000,"no free slots in PMChildFlags array",,,,,,,,,""
> 2019-09-20 02:00:24.505 UTC,,,109949,,5d8432b8.1ad7d,1,,2019-09-20 
> 02:00:24 UTC,,0,ERROR,58P01,"could not open shared memory segment 
> ""/PostgreSQL.2520932"": No such file or directory",,,,,,,,,""
> 2019-09-20 02:00:24.505 UTC,,,109950,,5d8432b8.1ad7e,1,,2019-09-20 
> 02:00:24 UTC,,0,ERROR,58P01,"could not open shared memory segment 
> ""/PostgreSQL.2520932"": No such file or directory",,,,,,,,,""
> 

Postgres version?

OS and version?

What was the database doing just before the FATAL line?

> what could be the possible reasons for this to occur and is there any 
> chance of database corruption after this event ?

The source(backend/storage/ipc/pmsignal.c ) says:

"/* Out of slots ... should never happen, else postmaster.c messed up */
         elog(FATAL, "no free slots in PMChildFlags array");
"

Someone else will need to comment on what 'messed up' could be.

> 
> 
> Regards,
> Bhargav
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com