Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ftZmd-0004lp-5x for pgsql-admin@arkaria.postgresql.org; Sat, 25 Aug 2018 14:43:24 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1ftZmY-0003sh-0b for pgsql-admin@arkaria.postgresql.org; Sat, 25 Aug 2018 14:43:18 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ftZmW-0003sa-09 for pgsql-admin@lists.postgresql.org; Sat, 25 Aug 2018 14:43:17 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ftZmO-0006zw-2w for pgsql-admin@lists.postgresql.org; Sat, 25 Aug 2018 14:43:15 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 804E721C1A; Sat, 25 Aug 2018 10:43:05 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Sat, 25 Aug 2018 10:43:05 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anarazel.de; h= cc:content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=jerIzV741qcLCOV96qnbBSAtzjOBiPOYB29IIrsXjOI=; b=wXk9aL1+ czU1WL6tCtEaBINSsHNskH40Vg761pGzUKL5XpvUrcZjGC5Fw31tzGFDUPKpMPhf BHunTJ/iSqaY7cNczFVbI4Nb+lg+FYmYM74vN0JENGz0xxFDs2FQPketaMVMnXXY g2DC285ZDBYIvHLsEHB7w2FtlbVvBngf6oZ6RGswdGsgBKAfFvd45tx1ogLizdps 01PJNuPzy7nE70BMWOBZGTF65kkQY8G8Rnqgq8BQHyJwIPr0wAAidWsUd+2JyHGW 7zWMR7xzKqinNmVTS2U1DeLjBolBZys5pP/oTdA15wAlJBk9zBzuCUgMP4022vuT rmBlezarVLz0SQ== 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-sender :x-me-sender:x-sasl-enc; s=fm3; bh=jerIzV741qcLCOV96qnbBSAtzjOBi POYB29IIrsXjOI=; b=o+HK1pMjb8Dra6BA2Lu4oMDbmSwE8kUQGY5IIsSPRWsf6 kyOjd5X//ic+BB6+JxSPRyJ/Kv7PGGCskeebw44pWA5fB4POFOHeh4WdzdGxkqph Pjiw4JKhaSjafbTPTOnhc+4VzphalF3nu3jOcp8n0CiyrF1iczwzxgKwGpgzbuop HX/Va3oNadEFpFWKyL3dz+yqhs4gXn1nksRRVGFv2CUBgXFNQSpYOZ5dPxok+bPl geqpKdK70wBG/owwk5j+tUshYoTxyZ4Nil6TGPYACruC5EwjBXusbL1HjPRGjMsu si3PhFkqa22actaUfZin1L9Qs8xAQ90wzZXjat1mw== X-ME-Proxy: X-ME-Sender: Received: from intern.anarazel.de (c-98-210-140-171.hsd1.ca.comcast.net [98.210.140.171]) by mail.messagingengine.com (Postfix) with ESMTPA id C8E7F10269; Sat, 25 Aug 2018 10:43:04 -0400 (EDT) Date: Sat, 25 Aug 2018 07:43:03 -0700 From: Andres Freund To: Julien Riou Cc: "pgsql-admin@lists.postgresql.org" Subject: Re: ERROR: no known snapshots Message-ID: <20180825144303.2cbtf7fyor7mkpvm@alap3.anarazel.de> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2018-08-25 07:04:14 +0000, Julien Riou wrote: > Hello, > > We have few highly available clusters with patroni managing PostgreSQL > 9.6 (pgdg on debian stretch). We use logical decoding with wal2json to > stream data to a remote platform. On a majority of clusters, it works > like a charm. But for one, we have the following error right after > decoding start: > > [1353-1] LOG: starting logical decoding for slot "*****" > [1353-2] DETAIL: streaming transactions committing after 321/292C06F0, reading WAL from 321/28BA9898 > [1354-1] LOG: logical decoding found consistent point at 321/28BA9898 > [1354-2] DETAIL: There are no running transactions. > [1355-1] ERROR: no known snapshots > [1355-2] CONTEXT: slot "*****", output plugin "wal2json", in the change callback, associated LSN 321/2A985A30 > > The only reference of the "no known snapshots" error is in PostgreSQL source > code: > https://git.postgresql.org/gitweb/?p=postgresql.git;a=blob;f=src/backend/access/heap/tuptoaster.c;h=ade4bd142dfbd7ef3340495b06d1041e4032a17f;hb=ca3489e768990e32096f0f24d46d5f0b8b70cff4#l2320 > > Do you know what can cause this error? Any chance that you're specifying the "include_unchanged_toast" option? I briefly looked over wal2json (which isn't part of PG) and as far as I can tell that option simply can't work correctly, and would cause errors like the above. Greetings, Andres Freund