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 1k6aJC-0005Qy-Uk for pgsql-general@arkaria.postgresql.org; Fri, 14 Aug 2020 14:03:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1k6aJA-0001QK-5f for pgsql-general@arkaria.postgresql.org; Fri, 14 Aug 2020 14:03:48 +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 1k6aJ9-0001QC-Tg for pgsql-general@lists.postgresql.org; Fri, 14 Aug 2020 14:03:47 +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 1k6aJ7-0002ak-JL for pgsql-general@postgresql.org; Fri, 14 Aug 2020 14:03:46 +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 07EE3hWb572935; Fri, 14 Aug 2020 10:03:43 -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: <1597410304614-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> Comments: In-reply-to PegoraroF10 message dated "Fri, 14 Aug 2020 06:05:04 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <572933.1597413823.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Fri, 14 Aug 2020 10:03:43 -0400 Message-ID: <572934.1597413823@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk PegoraroF10 writes: > This is the way you can test to push your server immediatelly to recover= y > mode. This one you=C2=B4ll get the problem instantaneously, differently = from the > last one which you have to wait a long time to happen. When I try this I get ERROR: operator does not exist: smallint =3D text LINE 2: ...eber_ID) filter (where ((status <> 6) or (TipoRecebimento in ^ HINT: No operator matches the given name and argument types. You might ne= ed to add explicit type casts. which makes me wonder whether you've got a buggy custom operator. regards, tom lane