From: Tom Lane <tgl@sss.pgh.pa.us>
To: sireesha <sireesha.padmini@gmail.com>
cc: pgsql-admin@lists.postgresql.org
Subject: Re: Mutex error 22 - Postgres version 14
In-reply-to: 
 <CAAM4KK3_J1bpv6ZHgZiC8_zKNrCp1AA747qUFRaL13Qubf5VKw@mail.gmail.com>
References: 
 <CAAM4KK3_J1bpv6ZHgZiC8_zKNrCp1AA747qUFRaL13Qubf5VKw@mail.gmail.com>
Comments: In-reply-to sireesha <sireesha.padmini@gmail.com>
	message dated "Wed, 01 Feb 2023 13:45:12 -0800"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1423180.1675289897.1@sss.pgh.pa.us>
Date: Wed, 01 Feb 2023 17:18:17 -0500
Message-ID: <1423181.1675289897@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1423181.1675289897%40sss.pgh.pa.us>
Precedence: bulk

sireesha <sireesha.padmini@gmail.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