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 1gtOgq-0002MI-M2 for pgsql-general@arkaria.postgresql.org; Tue, 12 Feb 2019 03:24:56 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gtOgo-0002O4-MY for pgsql-general@arkaria.postgresql.org; Tue, 12 Feb 2019 03:24:54 +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 1gtOgo-0002MV-A4 for pgsql-general@lists.postgresql.org; Tue, 12 Feb 2019 03:24:54 +0000 Received: from wout2-smtp.messagingengine.com ([64.147.123.25]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gtOgl-0004XW-J6 for pgsql-general@postgresql.org; Tue, 12 Feb 2019 03:24:53 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 3C6A53026; Mon, 11 Feb 2019 22:24:50 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Mon, 11 Feb 2019 22:24:50 -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=SKXHJJhMCQVk1/yDYEHWwQValf9 XWnpNH1XOwsRQAwc=; b=G+rn7hmaPPe4IrS1EOe+u+EAqUadFKrFdmDOf0FNq9O jU3+QLw3NygnCGOmaP4GX6EQLflu1fn8NRquf2rD+8qtdAWV8ZuGUkwW0p44YvS0 yQE0gDeQKmsl88A6FNjomindttUdd5dxNvbOV/jCb7WP6AZYc9ZJI611yzBuRp6Z rSWh9bCE4jeEDljXyVU1o5eZK+3gcMIFym81j+bM+UtgfFLdaGXrP99MDmfYKEBV wLoidNxfYba9F/TG9MozSURojcQ5wSDlZ1FO3qvLsOJ9zlfb5+xmHrkpI8jYlPqm WLRKinaMhoAzy5qvBdpFA6kDOs/4jzqlWtbJWcOO2ig== 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=fm2; bh=SKXHJJ hMCQVk1/yDYEHWwQValf9XWnpNH1XOwsRQAwc=; b=Qwg0mqRMnLv5j2Bt+/X1zO mPys+AmuB0YvqqWuxQDYz7xF2KjRjFlrsbjVeTLvqfGZBlBsDiBsgFI08VuHFNEl 4y8lGIjm01ga9hGnJMX2aPZTxTp5nWEL+R4NtDUj8ohklLg4TMn7cFPfkRzo/Dwt u/f5XTOvTCVAj5Hi/PkWoib+y8QRt10RXrYTp10/sDvpap3ewSJl7pou+K0awRVc vdrTeswvHeYdSWsgDeJKkpVtL0w3/qSYfjw7XBA8pY2j9mMLuAX56NyCEq9F+FLs Urtbsv+zVPDjGNZUN2ZLITaTEBbpn6E00LPoJFD9TQFtdd74oPO40+92e5WSyJGQ == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledruddttddgheejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfquhhtnecuuegrihhlohhuthemucef tddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenfghrlhcuvffnffculdejtd dmnecujfgurhepfffhvffukfhfgggtuggjsehgtderredttddvnecuhfhrohhmpefoihgt hhgrvghlucfrrghquhhivghruceomhhitghhrggvlhesphgrqhhuihgvrhdrgiihiieqne cukfhppeduudekrddvgedurddvgeelrddukedvnecurfgrrhgrmhepmhgrihhlfhhrohhm pehmihgthhgrvghlsehprghquhhivghrrdighiiinecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from paquier.xyz (mp76f1f9b6.ap.nuro.jp [118.241.249.182]) by mail.messagingengine.com (Postfix) with ESMTPA id 2B02DE4412; Mon, 11 Feb 2019 22:24:45 -0500 (EST) Date: Tue, 12 Feb 2019 12:24:32 +0900 From: Michael Paquier To: rob stone Cc: Justin Pryzby , PegoraroF10 , pgsql-general@postgresql.org Subject: Re: Server goes to Recovery Mode when run a SQL Message-ID: <20190212032432.GH1475@paquier.xyz> References: <1549209182255-0.post@n3.nabble.com> <1549209942200-0.post@n3.nabble.com> <1549660293178-0.post@n3.nabble.com> <20190209214651.GP31721@telsasoft.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="lrvsYIebpInmECXG" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --lrvsYIebpInmECXG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Feb 10, 2019 at 03:15:38PM +1100, rob stone wrote: > Down around line 87 onwards there are generate_series without any > parameters, and further dubious usage of EPOCH, as well as DOW. >=20 > Not having the table definitions is obviously clouding the analysis. That seems like the root issue for now. > If there is a bug in the parser, then one of the experts will have to > opine about that. If you actually extract the SQL query and the schema which are used to make the problem reproducible? That would help a bit instead of having to guess based on the sparse information on this thread. -- Michael --lrvsYIebpInmECXG Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAlxiPHAACgkQnvQgOdby QH1Tcw//Vh+ltkuvivolOH+60Jw6gpbX63DguomGuUr85AbuctBkROeyl/9zL77u qX0Nj4ZGNhQuJ70nYojFPL466UUeey+NpJtoe57p/oCbUYPIp+WhhmQvdQR48PL2 KN4W2EkRpjqOBaADfoVOvapuRfDxVZBT9OOAqikiF7/xP9Q1FvYSYGR1gu79uWaJ d7ePtVcMczGoWhvrONtDx8Rr6gH/xfge4M7MhFa6yyqoxdenp1eaRTJxwO0/QUyp FuPe8gv11t2/dOpMF7b3i49B2JZ3Fi8N0JlUuV5syUwNyZaUTGUhRnufd/Q8MRRM jmUHAtZI2j5wEYFHp0xbq8hMRlfj4V9RIhPd3DCY7FWnLhlOmv9gdi/7h1SeUwCz mwvrKuh7Zr1vhxjIHY1y+LNS5SmP68KN4OGCNVQFrnIq0X0EKU1s2YzEtPRRUdHZ AFUqIK/yvtwDWFnO7kgO/Md4t3amQoKHsW1JEh4D9exegokQEbS5v/sbkbxmNbr+ 9laEIZL+Ey/TyR8LJtj4RJxum20A09AQkWqRmWW3J6GS7JpT439Gn9HDSm97L7+I VmXyxpUjBKzL43hbeq3Z5uTuIstzaFZSMdzCJBJTFNgZHObo3e6D2bQNyHKoLbtD 6x6B4jhJLAwhG577hoG9m2MuCjoxxAVOwp7Vd+EmKwVb57Z6lOY= =5GJT -----END PGP SIGNATURE----- --lrvsYIebpInmECXG--