Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gqXFx-0007FA-H6 for pgsql-general@arkaria.postgresql.org; Mon, 04 Feb 2019 05:57:21 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gqXFv-00043e-N6 for pgsql-general@arkaria.postgresql.org; Mon, 04 Feb 2019 05:57:19 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gqXFv-00043X-9K for pgsql-general@lists.postgresql.org; Mon, 04 Feb 2019 05:57:19 +0000 Received: from mail-pl1-x62a.google.com ([2607:f8b0:4864:20::62a]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gqXFs-0005XL-GC for pgsql-general@postgresql.org; Mon, 04 Feb 2019 05:57:17 +0000 Received: by mail-pl1-x62a.google.com with SMTP id g9so6310041plo.3 for ; Sun, 03 Feb 2019 21:57:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:subject:from:to:date:in-reply-to:references:user-agent :mime-version:content-transfer-encoding; bh=YSSVDJMTuiB7/yA0RbYVA5EG5MAgXoqU/jlCV3BZVBQ=; b=INerYCeHH1+UUgKaEc9fTVem4x6/I2B8qDMlGNeh3RPs1rBN01saBYML0UcD+y7dQG PKUv0yBLWWcrpLiImAM6sVvwodaPxX7jm3r0Tzo6MjTmImQk1cJRNey4bGdXkys72q7n MA9wMkVzTj0B4/meFsLU2zTTy02LfaJQUN5lRl3JfyZxXvLfwoFvZJVRoLvVu5woTM2/ PwNW5+3iS4ergyDNnJXuGyojOiMhPr4v1WnUX6uf4oGIkcO9BaHS1OR0sPd7NOIQbzWe bIXj9MmYceWc82t9UVRMQoZ/IVxAv/FFd/FrI2hysy1U6amGXAXTjelym4NzJYFFdLRe hI7g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=YSSVDJMTuiB7/yA0RbYVA5EG5MAgXoqU/jlCV3BZVBQ=; b=MzvqT/LWXnR1vghZAOYjtHnhdChRFjJXLHanQmwhaS8v7oJFZcw8msYmSExc6DwcSZ 70ZQw9u1HItBFEKh/JNPypK9rNrEnXdryOo9U7ny/VOWS90qdTWbMhbxHC8Ab/RJhq+8 x5OEtqNS+/7+wPQU4aT1h7zylJWabhbtX6pxYFJR8UPAeTN7J7KZ8q311v5KzUhU+Nko /ne4jQwz5ZZcYeAitl3vuO/WOIXhjZfCjJvvjUWRx6YYXodyvr1W7pMYq0aCY5AXOmNh WqCnbXgf10gmmh7LK/3SuoD7qtTZ4wLlZqqraGUfcQLmucbs5O2m2iCXFCfPwIviUUBE F0tQ== X-Gm-Message-State: AJcUukc3/0lJ/4KQFqM5e16VfTHbc3hxCp7tsfsIu67IFpiyJanV2289 q/+OiW0a18Ya5ZSPrqa7b5rGhHAP X-Google-Smtp-Source: ALg8bN4dmc71aHBmoUs33le8itJZxsWbIFrAf6lo30YnpQ7bED/IvX3BMl8L7QDlsWXnKC8v/EL3jA== X-Received: by 2002:a17:902:9f89:: with SMTP id g9mr50722976plq.214.1549259834638; Sun, 03 Feb 2019 21:57:14 -0800 (PST) Received: from 192-168-1-102.tpgi.com.au ([61.69.131.212]) by smtp.gmail.com with ESMTPSA id a13sm10565781pgq.65.2019.02.03.21.57.12 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 03 Feb 2019 21:57:14 -0800 (PST) Message-ID: <0689b9bcac79f7f5e76ed69dd4baea012d6a3d33.camel@gmail.com> Subject: Re: Server goes to Recovery Mode when run a SQL From: rob stone To: PegoraroF10 , pgsql-general@postgresql.org Date: Mon, 04 Feb 2019 16:57:10 +1100 In-Reply-To: <1549211574297-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> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.30.4-1 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Olá Marcos, > My original query, which worked for some days and then went to > recovery mode > was ... If it was working and then ceased to function, did any of the following occur:- 1) Postgres version changed? 2) OS version changed? 3) Schema changes affecting the tables/views used in your query? I assume that you have a development data base. Can you bump up the log level on that, run the query and see any errors in the log. Cheers, Robert