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 1ixBpY-0001FE-3t for pgsql-hackers@arkaria.postgresql.org; Thu, 30 Jan 2020 15:34:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1ixBpW-0003NI-Td for pgsql-hackers@arkaria.postgresql.org; Thu, 30 Jan 2020 15:34: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 <9erthalion6@gmail.com>) id 1ixBpW-0003NB-IW for pgsql-hackers@lists.postgresql.org; Thu, 30 Jan 2020 15:34:06 +0000 Received: from mail-wr1-x442.google.com ([2a00:1450:4864:20::442]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from <9erthalion6@gmail.com>) id 1ixBpT-0005AF-PS for pgsql-hackers@postgresql.org; Thu, 30 Jan 2020 15:34:06 +0000 Received: by mail-wr1-x442.google.com with SMTP id k11so4561246wrd.9 for ; Thu, 30 Jan 2020 07:34:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=BTERifyAFDlNtvXsUfNboLupXzjafeCmnDEP+BB0kW0=; b=MoK3ecbLE62TcumORJ9Trguel568Gox1ThbSvi+icpXWxlZzncCDI2LO/JucZqsiTu 28rJ6wgsq/pMeyGG0PEEEpuCFYzTd1V9R8UzeRroQyyGgx39gdqI33wKFe4JYskr56bv /AHqUm9rOHyLuPDHCHlVrFGkMKIVJKQkTA8KlP3fxwNR+wgvJkHJyEFoyEXEPdj7hsjD O0aTj9SFBOjTtwBDH1RH3rx98h/FCwpveZTafYlOv2GsMwjmBA8o42ZaH6NhxZkeskQl BCQGIyzV28F826smjefL5c2Md60JRRMki7xVmJLBrwcE6cPjPXEUsYY24PxRO/AaDMUR bnUw== 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; bh=BTERifyAFDlNtvXsUfNboLupXzjafeCmnDEP+BB0kW0=; b=RS7t/g5zuIoW0IBLSvTAjemQMI/SlJ/Oa4hK3muX+wDXhUd+cnASJLCJqEcAZJwRhd vjc3WzOjFUNr/Kw1Fq6zUjHb0tx+U+M2Fp5aTvwymzV10wbB9mJX25CWyTtDVWTbnRPi tDzwMOSh2UNE1rSol8c4a34cQzizaCZkm31zXt3fMaztHCU9FQ+u3Y9tqZpyMqgy3erz Y0aMnh6bpusQPDrXG/JdnRCO7vjpGZFdHnGq57LP3yx804yQ85Hr1tRKQ32Vb7s1rUlc 0z7puchxTEkRbJtusKNvhLN40DfPQKP6cDPrvWn1yAYGIHREKsGedDygUpDmsk9urLwJ HwXw== X-Gm-Message-State: APjAAAUqdPpsKJ2/pZF9WsBNMwYgQ/uOP27mgfQvZibqoDaA60qAHBnw HkSYL1ZoF9WmyALSIV2b+pM= X-Google-Smtp-Source: APXvYqxk0fuQp9UV6Pk4YFi/WgA0xFSge9ETt/73ydK4mGy8OD3XIA3fNgRLLutoZCRtesRKjNYSJg== X-Received: by 2002:adf:edc4:: with SMTP id v4mr6134282wro.336.1580398442331; Thu, 30 Jan 2020 07:34:02 -0800 (PST) Received: from localhost ([212.76.253.171]) by smtp.gmail.com with ESMTPSA id m21sm6944882wmi.27.2020.01.30.07.34.01 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 30 Jan 2020 07:34:01 -0800 (PST) Date: Thu, 30 Jan 2020 16:34:33 +0100 From: Dmitry Dolgov <9erthalion6@gmail.com> To: Noah Misch Cc: Tom Lane , pgsql-hackers@postgresql.org Subject: Re: SimpleLruTruncate() mutual exclusion Message-ID: <20200130153433.6gvgm723lzpgiogh@localhost> References: <20190218073103.GA1434723@rfd.leadboat.com> <20190628170628.GA1238361@rfd.leadboat.com> <29566.1564419497@sss.pgh.pa.us> <20190801065117.GA2355684@rfd.leadboat.com> <20191117115652.doqc77yu7kbrqwmk@localhost> <20191118061426.GA1173376@rfd.leadboat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191118061426.GA1173376@rfd.leadboat.com> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk > On Sun, Nov 17, 2019 at 10:14:26PM -0800, Noah Misch wrote: > > > I'm probably missing something, so just wanted to clarify. Do I > > understand correctly, that thread [1] and this one are independent, and > > it is assumed in the scenario above that we're at the end of XID space, > > but not necessarily having rounding issues? I'm a bit confused, since > > the reproduce script does something about cutoffPage, and I'm not sure > > if it's important or not. > > I think the repro recipe contained an early fix for the other thread's bug. > While they're independent in principle, I likely never reproduced this bug > without having a fix in place for the other thread's bug. The bug in the > other thread was easier to hit. Just to clarify, since the CF item for this patch was withdrawn recently. Does it mean that eventually the thread [1] covers this one too? [1]: https://www.postgresql.org/message-id/flat/20190202083822.GC32531%40gust.leadboat.com