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 1i2Ldr-0004e8-QY for pgsql-hackers@arkaria.postgresql.org; Mon, 26 Aug 2019 20:31:07 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1i2Ldq-00086Z-JR for pgsql-hackers@arkaria.postgresql.org; Mon, 26 Aug 2019 20:31:06 +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 1i2Ldq-000863-81 for pgsql-hackers@lists.postgresql.org; Mon, 26 Aug 2019 20:31:06 +0000 Received: from mail-wr1-x443.google.com ([2a00:1450:4864:20::443]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1i2Ldl-0007aQ-BB for pgsql-hackers@lists.postgresql.org; Mon, 26 Aug 2019 20:31:05 +0000 Received: by mail-wr1-x443.google.com with SMTP id s18so16591399wrn.1 for ; Mon, 26 Aug 2019 13:31:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=G6tki9m4eRu30j4/QeOJrli+q4hom+4xFTvs7OaNxFg=; b=VASRnrBzJhyHwgf2PBn8SBTnVtyCVTnIR4Ntgfhew7x9s3FCQzNoDaK+s9dEKwTF/C RpOinHGRmXD5g0gaXptOJMD730DvDMbXT7pWx98btA7edfILxjxcK54Q7uNppLgJLwBN XEdL7a83HGa0hiC2O0V0S16RVuyTxL+t7BmKbpqnicK3+alZqBREQ1GTZL76l10RMbXD yeIIX2aT3xVwu8V+ii4g0zq3o8yYtUiOr7U/ybLxJoJnQmhYvLdtFq9dJc0fSYkVNMT9 UjYVzCb7Cw3hCy1Z8r08DBJXxldl7DW58SekmjhF/IKHGv0BXMkDautaCER/TI06WK4C BHIQ== 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=G6tki9m4eRu30j4/QeOJrli+q4hom+4xFTvs7OaNxFg=; b=oC3sPzvYwN0mLUFr+lQdlqSO9ibl0uvuZn7cnLxB+qk/7uDKSrR1EmeujzmXWkKvn4 aWq2YHggIEmQ8xi2wTZ6DSQhisZLiJWD2+ke8YQSU8PG5cg+5VWc0KxyOQv5TbCpHgow XbN4dQRwX26AsACp8ab8UIj0wgw9iVwFKwSV+kAsQJJ8KB8fFjGD+rKr5B5WYQiAPw7h WV7qmcAD0W41WdWkyzYZaZLu579WjbwlgirAjbOLrWq8FyxQOJPDz4XSfuhgOf73/Ijg qbZmiBFkGeeVZ86bBv9XBgKG0JP97/Lpnd1c0Z3yBDlqFAWDNheRGcOseRXfpOl3BOUg QLdA== X-Gm-Message-State: APjAAAXnfeb57RcgHysi1uBmihAPrW+pmyuom7B+U5t9jAp38O1/wTFy F/l6H1pD+r6F59x4dZyF6uUOmw== X-Google-Smtp-Source: APXvYqyEkDNtnkfh5pkPZqAUr4b1xx8Sej/lHRQ5HoOn8jve3zZhlsrbglRuRdRtr8aD4TWetJMcHA== X-Received: by 2002:adf:f991:: with SMTP id f17mr5569242wrr.233.1566851007640; Mon, 26 Aug 2019 13:23:27 -0700 (PDT) Received: from localhost (ip-86-49-234-190.net.upcbroadband.cz. [86.49.234.190]) by smtp.gmail.com with ESMTPSA id c12sm10481127wrx.46.2019.08.26.13.23.26 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 26 Aug 2019 13:23:26 -0700 (PDT) Date: Mon, 26 Aug 2019 22:23:25 +0200 From: Tomas Vondra To: Tom Lane Cc: Michael Paquier , Andres Freund , Thomas Munro , PostgreSQL Hackers Subject: Re: subscriptionCheck failures on nightjar Message-ID: <20190826202325.soqe6gmgnenbmzee@development> References: <30608.1550080759@sss.pgh.pa.us> <20190213181225.fathyapig4sm4exa@alap3.anarazel.de> <31663.1550082243@sss.pgh.pa.us> <20190213183303.ns54frt7cmvo6pgg@alap3.anarazel.de> <1466.1550085086@sss.pgh.pa.us> <20190213215147.cjbymfojf6xndr4t@alap3.anarazel.de> <20190813080435.GL2551@paquier.xyz> <20190826132904.3ayuw36qzl2c4ktr@development> <30652.1566831680@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <30652.1566831680@sss.pgh.pa.us> User-Agent: NeoMutt/20180716-1444-295967 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Mon, Aug 26, 2019 at 11:01:20AM -0400, Tom Lane wrote: >Tomas Vondra writes: >> I'm willing to take a stab at it, but to do that I need a way to >> reproduce it. Tom, you mentioned you've managed to reproduce it in a >> qemu instance, but that it took some fiddling with qemu parmeters or >> something. Can you share what exactly was necessary? > >I don't recall exactly what I did anymore, and it was pretty fiddly >anyway. Upthread I suggested > >>> Now that we know where the problem is, you could probably make it highly >>> reproducible by inserting a sleep of a few msec between the rename and the >>> second fsync. > >so why not try that first? > Ah, right. I'll give that a try. regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services