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 1gqSjJ-0000ae-Pj for pgsql-general@arkaria.postgresql.org; Mon, 04 Feb 2019 01:07: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 1gqSjI-0006Cr-H7 for pgsql-general@arkaria.postgresql.org; Mon, 04 Feb 2019 01:07:20 +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 1gqSjI-0006AN-3h for pgsql-general@lists.postgresql.org; Mon, 04 Feb 2019 01:07:20 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gqSjF-00073u-E0 for pgsql-general@postgresql.org; Mon, 04 Feb 2019 01:07:18 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id A59EF21FBA; Sun, 3 Feb 2019 20:07:16 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Sun, 03 Feb 2019 20:07:16 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm3; bh=AycvqK+msZaY+BFtMa45vMcYsxp ps4/nHZE9ezCBnNo=; b=ruM9K3U3tGc7KqscMxbEHeHM22jCdJzIzcEhpfUfcSv mqBmhcZvVEGpUXDoY/VSzf0cO1J8AJ2RzzTn6GeCiR6MGAZHXSYY1UPAq71lb1fU Em/BmJoRa7s/NebygiaHwocgpYmYPWXl8+9h90z22oZKif242YPmF3f9oPg8tvMW ip5NewBaDkNYFJTcCx6G1Qcx9Pi65L9s7BXq4nwB8b5MPNbVgPggvGPuekyc9gYn X/+DQoTcfRrnsA+xQypZ5xZwbD1GuUkSkV9Gmny7qxwhIzbqvb1jrj1bK2iOGEBh np9zuk6zWZIhCD/Q2tuCUCsoO3OUVlmdnyRwyM13COA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=AycvqK +msZaY+BFtMa45vMcYsxpps4/nHZE9ezCBnNo=; b=Ij/3fVoY29Epu3alVIxlkh ngcdrQYGIt0tFikohehuAym2bMKCb7c44GLKB5VTnqOhyG5A2UtFApkyvCmHvy2C oMxaidICMMBZ6LP2+hyqocne9P9D8CtS+Bd7TYcAXqbrzng/EM3RS8LnvZXoOU15 HZWohFNyrEQswRxuAeBBhqF1aVsqYIVX9Vv55VeBm5cTjmysfKQZRVzbBKPvWuxR XgoKqB+2zZQtLlWABM7t356/grMRti9pLfIQUxZq05vaom0JjRR62GG7Y2Vsfs5n k9JhXAgylPDkBdR2rmknOtJC91wgw+f4aCnK6FrFg+2n3puqQ5IrPyer5qopmiuA == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrkeefgddvkecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthenuceurghilhhouhhtmecufedt tdenucesvcftvggtihhpihgvnhhtshculddquddttddmnegfrhhlucfvnfffucdlfeehmd enucfjughrpeffhffvuffkfhggtggujgesghdtreertddtudenucfhrhhomhepofhitghh rggvlhcurfgrqhhuihgvrhcuoehmihgthhgrvghlsehprghquhhivghrrdighiiiqeenuc ffohhmrghinhepphhoshhtghhrvghsqhhlrdhorhhgnecukfhppeeiuddrvdduhedrudef jedrudeivdenucfrrghrrghmpehmrghilhhfrhhomhepmhhitghhrggvlhesphgrqhhuih gvrhdrgiihiienucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from paquier.xyz (c137162.net61215.cablenet.ne.jp [61.215.137.162]) by mail.messagingengine.com (Postfix) with ESMTPA id 77BB510087; Sun, 3 Feb 2019 20:07:13 -0500 (EST) Date: Mon, 4 Feb 2019 10:07:09 +0900 From: Michael Paquier To: Adrian Klaver Cc: PegoraroF10 , pgsql-general@postgresql.org Subject: Re: Server goes to Recovery Mode when run a SQL Message-ID: <20190204010709.GC1881@paquier.xyz> References: <1549209182255-0.post@n3.nabble.com> <37bc715f-12e2-84ac-6492-88d7b6306777@aklaver.com> <1549211574297-0.post@n3.nabble.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="DIOMP1UsTsWJauNi" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --DIOMP1UsTsWJauNi Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Feb 03, 2019 at 10:05:46AM -0800, Adrian Klaver wrote: > On 2/3/19 8:32 AM, PegoraroF10 wrote: >> I have a complex query which puts my server in recovery mode every time I >> run it. >> I don=B4t need to say that recovery mode is a situation you don=B4t want= your >> server goes to. Do you mean that your server crashes after running a SQL query? That could be a bug. > Well actually that is how standby_servers run: >=20 > https://www.postgresql.org/docs/11/warm-standby.html >=20 > "... while each standby server operates in continuous recovery mode, read= ing > the WAL files from the primary." >=20 > Is this server a standby? If you could post a self-contained test case, that would be really helpful to see if there is an actual bug. You can obfuscate the schema if need be, as long as the problem can be reproduced that's fine. -- Michael --DIOMP1UsTsWJauNi Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAlxXkD0ACgkQnvQgOdby QH0qhQ//f5PqWMBbnwd5ebCS9MobKiCZwc1vlBLloZV7+dV1cuMLsTflJgc/0ZWB XGNFfeZTbVb2nHnqW6V+FCbxSovVZBZoTLrip1wsdll34ThNLEV43ixJdtkllfy1 E2U7fA6TnXzxcgodmk8u6RHZ95qHR7irGKPj5KXvmLubiNwDGX4RW3Q+3DPwbOrK P5uIBy68uVPEPZdH0UYC8tG6pqZVAwigzhEV+iWp6ACANrfnVxjwS9fJhi0+rgDc 9/ASwr9vj+FpOdPq6FfH711yp0tjEr5sxWZHwqKd66OtAiIl/+z74hXlEh4UwDbH 5/K2qJ2ZexzuLaI9n9TJJFL+IJLSKVYetZe5AJy7mQRxSo7Z08Ymrdmfh0eYwqpu ori8vKpnSetrIegBi/PGRuRvQtyGl4eQ92lBAurNbfaqXLdF1BGFKdahAsbPkyOW tSSJrBJfiBkuLJ39A2pfZxWqwgmf9+S0YgO0IqykAWb/bQmfCMu/XoItrPaHWqU7 ZSSI6gLzTEQq2oyjkvBLVh9ydp45dxuTq8GYqJPa/J+042ViCGlXr97cLlcd2aHX WNg0OkF2t+x/Hh0hPBofZUL1wbkTFJS2Il9cE8fwU+o1rDT4/Oe+Q454WpPKQrZl 3fTsjR6VFKgKVUAqknHTThpjLNxNJaIUEtquPXtdjIvltIWD7TM= =xCQH -----END PGP SIGNATURE----- --DIOMP1UsTsWJauNi--