Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tYoO1-00FUOv-RB for pgsql-hackers@arkaria.postgresql.org; Fri, 17 Jan 2025 15:35:54 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tYoO0-000dJG-FG for pgsql-hackers@arkaria.postgresql.org; Fri, 17 Jan 2025 15:35:52 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tYoO0-000dID-5h for pgsql-hackers@lists.postgresql.org; Fri, 17 Jan 2025 15:35:52 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1tYoNx-0002ba-2C for pgsql-hackers@lists.postgresql.org; Fri, 17 Jan 2025 15:35:52 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2025010100; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description; bh=rLLbA6PCurHpt/qszCll01hPfea/QMyHMpOMyfvU5sA=; b=rZj4g ZXCC8JyTJ8Yh08rexv8i9uhSBVyAAESVeDbnxdFoXenqQuknRiaI3ZhpRNGNfDWNvCnp3N58hdQU0 rWbftD1fZMeQL1VG7t5kxR6EUVKzWRYBfbvdQ0TZyfWEZUfZVeEJlZ8kAeFm74cxQ9C0jmZOM7l90 FC0ddO08el1S4C3svvIXYc5K2xCKx3IygYvyUUkiherBAz4lGBMsZXZgVi9g1xICogUHN3yjApEnh jXHQP1IzByoxgNWI+MpXtpP+Kz5OFGCWGGw7iEzHzKs+D8XFydZ36ABU06ZLNOBqOzZ3X9Ga2S+bJ z5kUVmCwIb8TEW86LDx3ICUIzQAhg==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1tYoNw-00D8b2-2P; Fri, 17 Jan 2025 10:35:48 -0500 Date: Fri, 17 Jan 2025 10:35:48 -0500 From: Bruce Momjian To: Pavel Stehule Cc: PostgreSQL Hackers Subject: Re: Fwd: Re: proposal: schema variables Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, Jan 17, 2025 at 04:32:07PM +0100, Pavel Stehule wrote: > This discussion was around 2017 when I wrote a proposal and I hadn't a feeling 2017 is seven years ago so it would be good to get current feedback on the desirability of this feature. > There is one stronger argument for session variables - we are missing global > temporary tables. It is a real > limit and more times I found users with bloated pg_class, pg_attributes due > using temp tables. I don't believe > so we can have a global temp table - it is a significantly more difficult task > than session variables. At the end > session variables are trivial against global temp tables, and can replace > global temp tables in some use cases. > And the solution can be nicer, cleaner, safer than with a workaround based on > GUC. So this feature would be like global GUC variables, with permission control? -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.