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 1ffP67-0004tr-Kf for pgsql-hackers@arkaria.postgresql.org; Tue, 17 Jul 2018 12:28:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1ffP65-0000VS-Vl for pgsql-hackers@arkaria.postgresql.org; Tue, 17 Jul 2018 12:28:53 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ffP65-0000VL-LK for pgsql-hackers@lists.postgresql.org; Tue, 17 Jul 2018 12:28:53 +0000 Received: from mail-qt0-x241.google.com ([2607:f8b0:400d:c0d::241]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ffP62-0005TF-2h for pgsql-hackers@postgresql.org; Tue, 17 Jul 2018 12:28:52 +0000 Received: by mail-qt0-x241.google.com with SMTP id y5-v6so626574qti.12 for ; Tue, 17 Jul 2018 05:28:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=from:subject:to:cc:references:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=MErE20zUylRLay7TEyYCIy4qdY1jw+M9Mpcn1zIwZA8=; b=wdKCMD83yMNAvLRT1P5sYBuoNIsMoSrugHrisnO8XmAlrxPL7RHGTQu2jrSW4NEhzp 6Pl/HtJL3TPmv6emFiN4HShPNvY6KzkWZJBwR3FvuFh+JU0fa5V9K15qbKx2xnRJ8vZr /UIKlxbJfpQpBVzuA0nDW6qg/H3UlfkI/f8wYOJL0r5hE71RhXYEYBXgTSrxyYkWRa6h L6T+Zg4RJY5NEIvCIEkLTycuMpPJiY2av/C1dreAc8/F73ekaS2zT++i7mR1Pvfs1AEK kaLkxWMzIpETvHa+NH976PJXjKWqc96FLwsX1V7CLFTl770/Tqk2KoLLhI2UwOEK9IM8 cfmw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:cc:references:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=MErE20zUylRLay7TEyYCIy4qdY1jw+M9Mpcn1zIwZA8=; b=DHtiytrM9rs2GmNR59GOs0Fo9kzYCGoMR8jbkB+vVSkux/+g+b1kSLsZK7d+MiBTaZ ec27v4fNkujV+8tAufaGUnNEXfGEiAFEcvztfefcaXJDy2Nq6naeHsWGdW4Bvfk69Kjc XqcwUm6ZcwuFvJuQNVFxU4zUJ1lxGtmdKbLHesK3yByVevh0+1qi9FFRtsux3RTGDUew KDJMotpbZZo/hX4E7GIVN3kJcUTtHzACYQ3pujBn9/MXZquTx6LAwrwZVWbVTzDrFqL3 SQCRvQKHfB5PEgWmVlSIverD/LIPtt+Sh4lTOXrxs3iTl0bfR0ihO4RJd/7Jo2vpv+D3 MDGQ== X-Gm-Message-State: AOUpUlGNb7Fee09iiDao3Ph4q4ebYyRlXksZUhc7mpTrOqiLdw24ug0w aFNisjcFf8VZZt3rLfByWZ4ZSiK4tYw0J0w/kb/LYLwKOe0Rg9xkwB04Cu8I4YGh+pzSYkrdndu JbRpxxiykzxAsDaQ0l8s/ymRFPzE8iwvMYw7ZEcZpQLkUZGOekjB/evGUy5amXnoyAHq27tWYzW ge56KPQNwT90kq X-Google-Smtp-Source: AAOMgpcHTiQ6m84qM8JuWc/EFpd2W5Ju+5O1cWs5+PEN2N540mSjYI0W4ymKWAawwOhkzjlwascm0g== X-Received: by 2002:ac8:611c:: with SMTP id a28-v6mr1277377qtm.130.1531830528893; Tue, 17 Jul 2018 05:28:48 -0700 (PDT) Received: from [192.168.10.146] ([98.122.175.38]) by smtp.gmail.com with ESMTPSA id l44-v6sm611077qtb.58.2018.07.17.05.28.47 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 17 Jul 2018 05:28:48 -0700 (PDT) From: Andrew Dunstan X-Google-Original-From: Andrew Dunstan Subject: Re: [HACKERS] WAL logging problem in 9.4.3? To: Michael Paquier , Heikki Linnakangas Cc: Robert Haas , "pgsql-hackers@postgresql.org" References: <20180105041040.GI2416@tamriel.snowman.net> <20180111.170355.123986255.horiguchi.kyotaro@lab.ntt.co.jp> <20180330.100646.86008470.horiguchi.kyotaro@lab.ntt.co.jp> <20180704045912.GG1672@paquier.xyz> <20180711033241.GQ1661@paquier.xyz> <08b11907-d0b2-c396-2978-ba5aac1972df@iki.fi> <026AD6A1-3396-47F4-B87E-77E3F139D166@iki.fi> <20180717000129.GA3388@paquier.xyz> Message-ID: <3c1cf991-8846-9a6f-c669-e21f8ea9a6a4@2ndQuadrant.com> Date: Tue, 17 Jul 2018 08:28:47 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <20180717000129.GA3388@paquier.xyz> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-MW List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 07/16/2018 08:01 PM, Michael Paquier wrote: > > > I doubt as well that we'd be able to catch all the holes as well as the > conditions where the optimization could be run safely are rather > basically impossible to catch beforehand. I'd like to vote for getting > rid of this optimization for COPY, this can hurt more than it is > helpful. Per the lack of complaints, this could happen only in HEAD? Well, we'd be getting rid of it because of a danger of data loss which we can't otherwise mitigate. Maybe it does need to be backpatched, even if we haven't had complaints. cheers andrew -- Andrew Dunstan https://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services