Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mlLHB-0006Dn-5d for pgsql-hackers@arkaria.postgresql.org; Fri, 12 Nov 2021 01:22:45 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mlLHA-0000Kf-3M for pgsql-hackers@arkaria.postgresql.org; Fri, 12 Nov 2021 01:22:44 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mlLH9-0000KW-Ic for pgsql-hackers@lists.postgresql.org; Fri, 12 Nov 2021 01:22:43 +0000 Received: from mail-oi1-x22e.google.com ([2607:f8b0:4864:20::22e]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1mlLH6-0007uX-LQ for pgsql-hackers@postgresql.org; Fri, 12 Nov 2021 01:22:43 +0000 Received: by mail-oi1-x22e.google.com with SMTP id 7so4787478oip.12 for ; Thu, 11 Nov 2021 17:22:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leadboat.com; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=Dzq0rr3b46Dolmum/wmjrfpu8Is10XueA7JSyshuulA=; b=LhZOMqVJWeTsgGbv9WpZ/VC72t9nKWNus+7uRqpM+0PeFFdQb4uh82IJ+f/HZra1+q 4bC+KtWXrGG1zLRTyILQJrd6UdvBIB/KVtvPDXSap/lczEpHrxfq4A6k7OaQJctWykL/ NN0UsXbKwyJwGLmopZkiTStL3UY5Y71Oucqsg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=Dzq0rr3b46Dolmum/wmjrfpu8Is10XueA7JSyshuulA=; b=X0HZiUXyvX347S+wOaQg/OBoR2qo9jdU3yPae9Tz+hxkykyIophy/3NQia9AtWjQX9 TtiTznHhWS/C3V8uL8dvItlRCtEFcSSZH1M8veOGApWjdrxIlzoHkqMP61YeY/EgrcRQ eBQ+X3DidXiU1KIZmYu8DwWewa1toVfDFO9F+vWWXTWS9blStcZj0NpFuKqX5eMcmX44 ZrJEAZjDnYSkExk9et9Yq3ZmLITGHgFFyBXysfFzx3RdSX7oJm9g3JdbsX7GKfb8ZCml +TG/5nPQDmqwUAEEbfWIWYYfRZdi9/KuSo23sVJzX7MtbHXR1GhTLSwfnq5j1sEkV9fI uyLw== X-Gm-Message-State: AOAM531HiljJ/sWkIQMzGTO+xutWLqXUw4uDClP8wJ0iuD8KXMTGbHAo KatQdBc5uPRUTQ2syM2rVBM5vrPt2oidsQ== X-Google-Smtp-Source: ABdhPJwsqCUv8fsjMNbYvMfbmgIKW7jsITMuD2iZJkMK7AlDXPaxZuSUiy7O2iUNu2LHKe/nkhombw== X-Received: by 2002:a05:6808:1403:: with SMTP id w3mr11712122oiv.80.1636680157196; Thu, 11 Nov 2021 17:22:37 -0800 (PST) Received: from rfd.leadboat.com ([2600:1702:a20:5750::46]) by smtp.gmail.com with ESMTPSA id x62sm1051497oig.24.2021.11.11.17.22.35 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 11 Nov 2021 17:22:36 -0800 (PST) Date: Thu, 11 Nov 2021 17:22:34 -0800 From: Noah Misch To: Michael Paquier , tgl@sss.pgh.pa.us Cc: pgsql-hackers@postgresql.org Subject: Re: XLogReadRecord() error in XlogReadTwoPhaseData() Message-ID: <20211112012234.GA1020314@rfd.leadboat.com> References: <20211107013157.GB790288@rfd.leadboat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, Nov 08, 2021 at 01:42:46PM +0900, Michael Paquier wrote: > On Sat, Nov 06, 2021 at 06:31:57PM -0700, Noah Misch wrote: > > On Sun, Oct 24, 2021 at 04:35:02PM -0700, Noah Misch wrote: > > > https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=kittiwake&dt=2021-10-24%2012%3A01%3A10 > > > got an interesting v9.6 failure [...]: > > > > > > 2021-10-24 14:25:29.263 CEST [34569:175] pgbench ERROR: could not read two-phase state from xlog at 0/158F4E0 > > > 2021-10-24 14:25:29.263 CEST [34569:176] pgbench STATEMENT: COMMIT PREPARED 'c1'; Tom Lane reported another instance today: https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=tadarida&dt=2021-11-11%2013%3A29%3A58 Each of the three failures happened on a sparc64 Debian+gcc machine. I had tried ~8000 iterations on thorntail, another sparc64 Debian+gcc animal, without reproducing this. > > As a first step, let's report the actual XLogReadRecord() error message. > > Attached. > > Good catch! This looks good. Pushed.