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 1gttfi-00083g-6t for pgsql-general@arkaria.postgresql.org; Wed, 13 Feb 2019 12:29:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gttfg-0007VW-CS for pgsql-general@arkaria.postgresql.org; Wed, 13 Feb 2019 12:29:48 +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 1gttff-0007V3-UX for pgsql-general@lists.postgresql.org; Wed, 13 Feb 2019 12:29:48 +0000 Received: from mail-pf1-x432.google.com ([2607:f8b0:4864:20::432]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gttfd-0006h0-4j for pgsql-general@postgresql.org; Wed, 13 Feb 2019 12:29:46 +0000 Received: by mail-pf1-x432.google.com with SMTP id q17so1065918pfh.10 for ; Wed, 13 Feb 2019 04:29:44 -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=jHntNY/YMCQJ6T9/yI4sj+Wu0mEwCBTbkVkvribq/fg=; b=fq7RTgEPqcP6oxLMBmRtPstwMskmO+bmh4aaf/J7Pet/OxqjSQQS8PtghMXj8SMAQK AQbcGRlLUlg2RxKFEwomqbvKNB0Wus7r5+uy+KUOEniZflKchhrK+G/1525a72aKyjTw NJ0niJ8Bx53ePQeB9kqVYESb89Au1zqhB2YDIrj0KCzTox12Vjl4vf/tVr+PmvLAjs3Z shqyGJDc4zqaTlOzgctxRNoqekWE3EKuutK18yrwVrDG95HSn2ZzBm8mEhqNd9qQLXSo MxThjsJH3kxeGThne4Hr2pLK4Xj6ke4l7xe1dsQHTlgdzk/b1XZuvE03cltAy7t7p93L HDTg== 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=jHntNY/YMCQJ6T9/yI4sj+Wu0mEwCBTbkVkvribq/fg=; b=cWNC3qqRAx/P/4xtevYAIcycQbq5+PcTEWnTPM5EvuXbPL5qWl7yPogsm0mCLrCpOO sncZ2ekWEJGp9kONvc4SgFxTGzRMDjz3huOAvsvx27TAd2ccaykggcrKgdqCgzbKTPPJ m1wGlAyhoJtgnFx2OZiQO11ml08MbvgC8pJJupVrX4e+nIZvFVn6Wg0p14wIizY2S+4X URRA4B1eS6rNsfCrPod9CeilxwDrXeTGD7P2mIBX7IjAIzIE0PN4GJwl21Ps5kvsQDS5 fbe+cLK0bbWY0vgNElUhn6OX8PlrPQAjC+uZrfCAhWunNCHeXXSWwDz+NT4zEPH5YuSl OoEA== X-Gm-Message-State: AHQUAubOl3bjgZRu+pj1E6XwaJ30BEZWtfU/1rnq4m9IFEDr5RLLDq2w HYEc8CIwLbfGCiJbimGeCVY= X-Google-Smtp-Source: AHgI3IZ7wB9rdXtaLR8BHRAuNp8cbqLc0tSBYA1ZotlCqm1Zb4+r7q/iLLE0ptIWMD4CkY6YzQwm+w== X-Received: by 2002:a63:f10c:: with SMTP id f12mr258809pgi.374.1550060982874; Wed, 13 Feb 2019 04:29:42 -0800 (PST) Received: from 192-168-1-102.tpgi.com.au ([61.69.131.212]) by smtp.gmail.com with ESMTPSA id w128sm23527870pfw.79.2019.02.13.04.29.40 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 13 Feb 2019 04:29:42 -0800 (PST) Message-ID: Subject: Re: Server goes to Recovery Mode when run a SQL From: rob stone To: PegoraroF10 , pgsql-general@postgresql.org Date: Wed, 13 Feb 2019 23:29:37 +1100 In-Reply-To: <1550058083109-0.post@n3.nabble.com> References: <1549209182255-0.post@n3.nabble.com> <1549209942200-0.post@n3.nabble.com> <1549660293178-0.post@n3.nabble.com> <20190209214651.GP31721@telsasoft.com> <20190212032432.GH1475@paquier.xyz> <1550058083109-0.post@n3.nabble.com> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.30.5-1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hello Marcos, On Wed, 2019-02-13 at 04:41 -0700, PegoraroF10 wrote: > Here is a SQL which will get that recovery mode. You can run it on > any database because we created it with FROM VALUES, so ... > But this one is that one which grows and grows memory use until all > memory and swap space are gone, so problem occurs. That other SQL > which gives us the same problem but immediatelly we couldn´t replay > it without our entire database. Even if we extract just that schema > to a new DB it doesn´t go to recovery mode. We will think a little > bit more to create something you can test. > Thanks for the revised query. However, the create table/view scripts are needed as well. Cheers, Robert