Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1k6dlD-0005w0-NX for pgsql-general@arkaria.postgresql.org; Fri, 14 Aug 2020 17:44:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1k6dlC-0005ZP-8l for pgsql-general@arkaria.postgresql.org; Fri, 14 Aug 2020 17:44:58 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1k6dlC-0005ZI-0v for pgsql-general@lists.postgresql.org; Fri, 14 Aug 2020 17:44:58 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1k6dl5-0004Vg-NZ for pgsql-general@postgresql.org; Fri, 14 Aug 2020 17:44:57 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 07EHinL6650988; Fri, 14 Aug 2020 13:44:50 -0400 From: Tom Lane To: PegoraroF10 cc: pgsql-general@postgresql.org Subject: Re: Server goes to Recovery Mode when run a SQL In-reply-to: <1597422849057-0.post@n3.nabble.com> References: <1549209182255-0.post@n3.nabble.com> <37bc715f-12e2-84ac-6492-88d7b6306777@aklaver.com> <1549211574297-0.post@n3.nabble.com> <20190204010709.GC1881@paquier.xyz> <1597265258319-0.post@n3.nabble.com> <323345.1597270142@sss.pgh.pa.us> <1597410304614-0.post@n3.nabble.com> <572934.1597413823@sss.pgh.pa.us> <1597422849057-0.post@n3.nabble.com> Comments: In-reply-to PegoraroF10 message dated "Fri, 14 Aug 2020 09:34:09 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <650986.1597427089.1@sss.pgh.pa.us> Date: Fri, 14 Aug 2020 13:44:49 -0400 Message-ID: <650987.1597427089@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk PegoraroF10 writes: > So, how can I know which custom operator is being used on that comparison ? You tell us. I don't know of any common extension that would create a "smallint = text" operator. (A variant theory is that you didn't make a new operator, but an implicit cast from smallint to text. Either way, it almost certainly is a homebrew thing. Or maybe what you are running is not stock Postgres?) It might be interesting to try some direct test, like SELECT 22::smallint = 'foo'::text; For me that gives the same "operator does not exist: smallint = text" error, but I bet your database tries to execute it. regards, tom lane