pá 17. 1. 2025 v 16:35 odesílatel Bruce Momjian <br...@momjian.us> napsal:
> 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? > + types and domain type check - holds data in binary form - there are not conversions binary, text + it is declared - so less space for misuse is there. Custom GUC are absolutely tolerant + it is a fully database object, only owner can alter it, and event triggers are supported, sinval + possibility to set mutability, default value Regards Pavel > > -- > Bruce Momjian <br...@momjian.us> https://momjian.us > EDB https://enterprisedb.com > > Do not let urgent matters crowd out time for investment in the future. > > >
