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 1lMwao-0004cl-0H for pgsql-hackers@arkaria.postgresql.org; Thu, 18 Mar 2021 17:37:54 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lMwam-0003qf-Sa for pgsql-hackers@arkaria.postgresql.org; Thu, 18 Mar 2021 17:37:52 +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 1lMwam-0003oy-Ln for pgsql-hackers@lists.postgresql.org; Thu, 18 Mar 2021 17:37:52 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lMwak-00020R-IC for pgsql-hackers@postgresql.org; Thu, 18 Mar 2021 17:37:52 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id A76405C00BC; Thu, 18 Mar 2021 13:37:48 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Thu, 18 Mar 2021 13:37:48 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:subject:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=9SqhTRfi5iiJlqgEUhG4cZQTdRMTwMmGIWbaulDPgWU=; b=cFavQFH5 WQnDDXGWBxwYm1CFtm4GdEpmknSPhrOFP34vYmDKMgIufUhCnpAECjf/2m2ODSCu JnPFWPf3dFeFIeqlnwkpQFPzoSNhCgajVhpAtF+LZPT/rLPOcfjWctMIrIniDjTa WsbI0M1kDy0EdbO3xtsvFKPb/EIe1PM6ZToGv6wj7IXLGBdEHq1YLMZw1fJlE41F sMIDlLqYg3N2tpC05/S2/V4CifHaC9zUVz7Fypm4Gho7V23y+Qyx/WFwX9zAPZpy KxTt6YsS2fnDwu2rRBnCyfdIUCAQfHKeL0ikoq7QEbe12cGWxISs24dblz4wcB6C 4unyk9Q36Drdaw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrudefiedguddthecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpeffhffvuffkgggtugfgjggfsehtkeertddtredunecuhfhrohhmpeetlhhv rghrohcujfgvrhhrvghrrgcuoegrlhhvhhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorh hgqeenucggtffrrghtthgvrhhnpeeufffhjeeiueeuffegvddukeegledtveeivdeiueef ieeivefgteehueefteehvdenucfkphepudeltddrleehrdduledrleehnecuvehluhhsth gvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprghlvhhhvghrrhgvsegr lhhvhhdrnhhoqdhiphdrohhrgh X-ME-Proxy: Received: from perhan.alvh.no-ip.org (unknown [190.95.19.95]) by mail.messagingengine.com (Postfix) with ESMTPA id 6B1A91080068; Thu, 18 Mar 2021 13:37:47 -0400 (EDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id F19422A0CAD; Thu, 18 Mar 2021 14:37:43 -0300 (-03) Date: Thu, 18 Mar 2021 14:37:43 -0300 From: Alvaro Herrera To: Stephen Frost Cc: Bruce Momjian , Masahiko Sawada , Tom Kincaid , Robert Haas , Andres Freund , Amit Kapila , Thomas Munro , PostgreSQL-development , Masahiko Sawada Subject: Re: Key management with tests Message-ID: <20210318173743.GA13514@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20210318172152.GJ20766@tamriel.snowman.net> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2021-Mar-18, Stephen Frost wrote: > * Alvaro Herrera (alvherre@alvh.no-ip.org) wrote: > > Patch 10 uses the term "WAL-skip relations". What does that mean? Is > > it "relations that are not WAL-logged"? I suppose we already have a > > term for this; I'm not sure it's a good idea to invent a different term > > that is only used in this new place. > > This is discussed in src/backend/access/transam/README, specifically the > section that talks about Skipping WAL for New RelFileNode. Basically, > it's the 'wal_level=minimal' optimization which allows WAL to be > skipped. Hmm ... that talks about WAL-skipping *changes*, not WAL-skipping *relations*. I thought WAL-skipping meant unlogged relations, but I understand now that that's unrelated. In the transam/README, WAL-skip means a change in a transaction in a relfilenode that, if rolled back, would disappear; and I'm not sure I understand how the code is handling the case that a relation is under that condition. This caught my attention because a comment says "encryption does not support WAL-skipped relations", but there's no direct change to the definition of RelFileNodeSkippingWAL() to account for that. Perhaps I am just overlooking something, since I'm just skimming anyway. -- Álvaro Herrera Valdivia, Chile