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.92) (envelope-from ) id 1jFjNM-00065N-2C for pgsql-hackers@arkaria.postgresql.org; Sat, 21 Mar 2020 19:01:40 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1jFjNK-00083u-HE for pgsql-hackers@arkaria.postgresql.org; Sat, 21 Mar 2020 19:01:38 +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_SHA1:256) (Exim 4.89) (envelope-from ) id 1jFjNK-00083n-15 for pgsql-hackers@lists.postgresql.org; Sat, 21 Mar 2020 19:01:38 +0000 Received: from mail-pf1-x444.google.com ([2607:f8b0:4864:20::444]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jFjNF-0003RF-ON for pgsql-hackers@postgresql.org; Sat, 21 Mar 2020 19:01:37 +0000 Received: by mail-pf1-x444.google.com with SMTP id z65so5162985pfz.8 for ; Sat, 21 Mar 2020 12:01:33 -0700 (PDT) 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=ERKKqMb/tNYnZpY2FpiZ37gbGh0A6u5PHoJW0FkjpG0=; b=cZAaJ+OzQ4GbF5T2xIOk2lN6OqgjkduBhi+K8iL4hUhy2mseS8UBsPZIDBvs+93v7V RlVjrMT3wpghIf3U8+SuKAbPZbNW+QYwQCfstHcqPLgjDS68zmfRdzjecmNTpIEkiDIJ G9FuCPQi9Lp8YUUkLgQLGqkLvebw8ZH1079sU= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=ERKKqMb/tNYnZpY2FpiZ37gbGh0A6u5PHoJW0FkjpG0=; b=lZEn0XW0KU80tIUUa8/lTYU/ZrcsdI2MZESGjCsV8ARcMrhspkpeCFM9emEuRvbi0l gvFVsl8/cfVMNICi82bMSHc9HeaImnGcRBy7yEdrBfsaj/rbb4/YxOg0yZAwF+YX1s4s XZSf/A6o3HGDYwHm48O1vn6Vn5an03qqvZaLI3dv3VnheEg2e0l8mMG9FNujnIMUbhGs qNHpLTVzAi4l804FRXAFw8wrhgSNIsOiHV0Eo0rUpbzNILSXKYz2KSiHk043+oQSici3 vfElQCD3LCRHOFQ3emO/D1BohRtoGhSlkw1d+5GLdQDzY+tNLH4DNBUdcduIOAFmvG/O blJg== X-Gm-Message-State: ANhLgQ1Fw4iJV52Vg9dNAvSuGwqsLdRaTZGoDyTw7Yj39UT+d1bj8NOA kNBAjN2UeP5qhDfqz97slBHcNw== X-Google-Smtp-Source: ADFU+vsO/mfZt16rzI70W6AYDP4uRWz262mjk9ZlsBVCpC0Kl57+2blFoVH3+hwHSQU3RJY+pXRDBA== X-Received: by 2002:a63:9d04:: with SMTP id i4mr14576180pgd.294.1584817290637; Sat, 21 Mar 2020 12:01:30 -0700 (PDT) Received: from rfd.leadboat.com (108-233-125-46.lightspeed.sntcca.sbcglobal.net. [108.233.125.46]) by smtp.gmail.com with ESMTPSA id b70sm9138635pfb.6.2020.03.21.12.01.29 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 21 Mar 2020 12:01:29 -0700 (PDT) Date: Sat, 21 Mar 2020 12:01:27 -0700 From: Noah Misch To: Kyotaro Horiguchi Cc: robertmhaas@gmail.com, pgsql-hackers@postgresql.org, 9erthalion6@gmail.com, andrew.dunstan@2ndquadrant.com, hlinnaka@iki.fi, michael@paquier.xyz Subject: Re: [HACKERS] WAL logging problem in 9.4.3? Message-ID: <20200321190127.GA1763544@rfd.leadboat.com> References: <20200227.160024.1603714516899165010.horikyota.ntt@gmail.com> <20200301195632.GA135286@rfd.leadboat.com> <20200302.165353.1408159864331844170.horikyota.ntt@gmail.com> <20200304.162919.898938381201316571.horikyota.ntt@gmail.com> <20200316034647.GA1121601@rfd.leadboat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200316034647.GA1121601@rfd.leadboat.com> User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Sun, Mar 15, 2020 at 08:46:47PM -0700, Noah Misch wrote: > On Wed, Mar 04, 2020 at 04:29:19PM +0900, Kyotaro Horiguchi wrote: > > The attached is back-patches from 9.5 through master. > > Thanks. I've made some edits. I'll plan to push the attached patches on > Friday or Saturday. Pushed, after adding a missing "break" to gist_identify() and tweaking two more comments. However, a diverse minority of buildfarm members are failing like this, in most branches: Mar 21 13:16:37 # Failed test 'wal_level = minimal, SET TABLESPACE, hint bit' Mar 21 13:16:37 # at t/018_wal_optimize.pl line 231. Mar 21 13:16:37 # got: '1' Mar 21 13:16:37 # expected: '2' Mar 21 13:16:46 # Looks like you failed 1 test of 34. Mar 21 13:16:46 [13:16:46] t/018_wal_optimize.pl ................ -- https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2020-03-21%2016%3A52%3A05 Since I run two of the failing animals, I expect to reproduce this soon. fairywren failed differently on 9.5; I have not yet studied it: https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fairywren&dt=2020-03-21%2018%3A01%3A10 > > It lacks a part of TAP infrastructure nowadays we have, but I > > want to have the test (and it actually found a bug I made during this > > work). So I added a patch to back-patch TestLib.pm, PostgresNode.pm > > and RecursiveCopy.pm along with 018_wal_optimize.pl. > > (0004-Add-TAP-test-for-WAL-skipping-feature.patch) > > That is a good idea. Rather than make it specific to this test, I would like > to back-patch all applicable test files from 9.6 src/test/recovery. I'll plan > to push that one part on Thursday. That push did not cause failures.