Re: Mutex error 22 - Postgres version 14

Hi Tom,

Thanks for the feedback.
This error is reported in Postgresql log and exact message from the log is
below .

2023-01-24 02:35:45.833 PST [3424807] LOG: PID 0 in cancel request did not
match any process
*Error locking mutex 22*

There are multiple mutex errors logged in postgresql.log and the Postgres
processes went to defunct state.
We couldn't access the database until we restarted the server.No logs
reported in server as well.

We noticed this behaviour in 2 different Postgres 14 databases in past 1
week.

Please let me know if i have to provide any other trouble report.

Thank you.

Regards,
PS

On Wed, Feb 1, 2023 at 2:18 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> sireesha <sireesha(dot)padmini(at)gmail(dot)com> writes:
> > We recently upgraded our production databases to 14 and we have
> encountered
> > Mutex 22 error and Postgres defunct processes in 2 of the databases.
>
> There is no part of Postgres that would produce a message like "Mutex 22
> error". You need to spend a bit more effort on identifying where your
> problem is coming from. If it does seem to be coming from Postgres,
> you need to spend a lot more effort on providing a useful trouble report
> if you want any help from the mailing lists. Please see
>
> https://wiki.postgresql.org/wiki/Guide_to_reporting_problems
>
> regards, tom lane
>