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 1gY0qL-0001oP-VS for pgsql-hackers@arkaria.postgresql.org; Sat, 15 Dec 2018 03:42:22 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gY0qK-0005SR-7T for pgsql-hackers@arkaria.postgresql.org; Sat, 15 Dec 2018 03:42:20 +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 1gY0qI-0005Pc-Jh for pgsql-hackers@lists.postgresql.org; Sat, 15 Dec 2018 03:42:19 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gY0qA-0004Rr-Cw for pgsql-hackers@lists.postgresql.org; Sat, 15 Dec 2018 03:42:18 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 5E6BF21DA6; Fri, 14 Dec 2018 22:42:08 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Fri, 14 Dec 2018 22:42:08 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm3; bh=cG5/mtvdkbZyat6tmOAq5ib8Jlm 7gKZFiFI7k8c4N64=; b=usKiu2oEYDl+O5xwegYj8EftCLKp7WH3NJvW+c0do3Q iT7azgJkRfrMqMUKd+odEJRWNQS8DMhOfQ9igfnQU/u9KQcAz749EgL5SlW224GG uXTtUSlngZvznuxbJSPubTTSHUBbXjsps9INU/iEoiLOpnesWrCKRSPeouqzi/WC /tIWd0iK6vGDKf1XZ+syQ2bUThHZXEgVXKXQDUR/wpXYzNR5sCkwxC/QtIxpKb1s nb0pIcvKj3J+lTPvnO92056seGNTM5qHHlgK6jNUypR3D/hmqlwBGlynum0g0iB5 cxbypyQFRks6TqT2w2LipjG71YV6kHjMeq+dODah7Ig== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=cG5/mt vdkbZyat6tmOAq5ib8Jlm7gKZFiFI7k8c4N64=; b=FdWDFgM1WZe402GNIPiqmI Jd5HvHCbOvD0z+Io5oH47lwDrQnlP8TDPpbqB+JRUd9D/NtFP7x3C4+tE7IlKXb6 PpMr0Vb5kHU4sSCmk5T7BckPPzJhjE9iKoyqMGz4fDJ/1G4DQzWi045Jg0Ti7PTo AcY2KGaYBm393RRNCoh8Wq/zhjw5QcJlp0P/Wk2SVnHxS3frU0Nw6Ef41i71Fppk tdBAR4FFE2Aj/6Pjymky2VeREGcHryBZwTuEjI3TMPUL+KToMpE8c6Vyca7XtDpa sOhct9+NmNs9xWllW9PHKwMNCXPPdKOWlhGg2fmpz0SGeRER345Nv4OCi/bptUIg == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtkedrudehiedgieduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfquhhtnecuuegrihhlohhuthemucef tddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenfghrlhcuvffnffculdejtd dmnecujfgurhepfffhvffukfhfgggtuggjsehgtderredttddvnecuhfhrohhmpefoihgt hhgrvghlucfrrghquhhivghruceomhhitghhrggvlhesphgrqhhuihgvrhdrgiihiieqne cukfhppeeiuddrvdduhedrudefjedrudeivdenucfrrghrrghmpehmrghilhhfrhhomhep mhhitghhrggvlhesphgrqhhuihgvrhdrgiihiienucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from paquier.xyz (c137162.net61215.cablenet.ne.jp [61.215.137.162]) by mail.messagingengine.com (Postfix) with ESMTPA id C5908E44D4; Fri, 14 Dec 2018 22:42:05 -0500 (EST) Date: Sat, 15 Dec 2018 12:42:03 +0900 From: Michael Paquier To: Alvaro Herrera Cc: Robert Haas , Tom Lane , PostgreSQL Hackers Subject: Re: removal of dangling temp tables Message-ID: <20181215034203.GF5012@paquier.xyz> References: <20181215020632.5vlffyvfpn4k42cn@alvherre.pgsql> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="j2AXaZ4YhVcLc+PQ" Content-Disposition: inline In-Reply-To: <20181215020632.5vlffyvfpn4k42cn@alvherre.pgsql> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --j2AXaZ4YhVcLc+PQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Dec 14, 2018 at 11:06:32PM -0300, Alvaro Herrera wrote: > I did propose in my OP the idea of a PGPROC boolean flag that indicates > whether the temp namespace has been set up. If not, have autovac remove > those tables. I like this option better, but I fear it adds more > ProcArrayLock contention. Maybe I can just use a new LWLock to > coordinate that particular member of the ProcGlobal array ... (but then > it can no longer be a boolean.) Isn't that what tempNamespaceId can be used for in PGPROC now? The flag would be set only when a backend creates a new temporary schema so as it can be tracked as the owner of the schema. -- Michael --j2AXaZ4YhVcLc+PQ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAlwUeAsACgkQnvQgOdby QH1dpw//e+cr47XoJjF986dZvEFiTNCtsYw+gVHHpSUB9Og5rllAohfT58Mk8uTj OOPrBAAPAehMoReDLsPKvlwWDueqsgOnTtI6a4oQSZxD1AtdmEC2NEi09hfxxN7L BGA367yHBduT7tgaQRfyMkpC1PzLjv0gkP6NgYUhDHmKOwI5+6OkTOylOMeqRq6V GQOllwPw4zp8meOBsepa1Ykv775JQLHal08DTshXHBMdTq1GSKKgtlxhqUkOo26s TiL0g/QS4qp3n1ZAq6XMumgyqr+PKj1XkV3kejuPaD4ltYIaC+q7BmqEV1p4+K7H JiPNjt53DB+p2fuU+f4nJTlwCt9CFv/Qp+ABQXbVKG7Ov3eUbVhaG98olQVu8CaH f+NomkpVXsGBud1wBT2GDfJmv0jvBaJCAETDkGFTBaaXi+M/O+KSct6kIroCIzp4 heT70VCDpc5rmCZod6fzubpRP3vxbvpMRJv30ylVGja68mSMLOW8H4OgOwjqfkce 2Ql0cYGYhEWFkuD8bLip6r/zGL3e9SZ1d8P3OMrKQcG9YLYDxStdWh4At4d3yZnD gHDEDJREbHdCssYI2zXeSLiqOqXLlgQNvkhvAK4iGIPfExE5ZPVsNr6KK7QGB8pM 2JtZMjZszSM8RzSxeOPc9Y7jOdnXadRLUVgt1B6EHwjkUPKiV6Q= =h4mx -----END PGP SIGNATURE----- --j2AXaZ4YhVcLc+PQ--