| From: | Wolfgang Walther <walther(at)technowledgy(dot)de> |
|---|---|
| To: | Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Erik Rijkers <er(at)xs4all(dot)nl>, Michael Paquier <michael(at)paquier(dot)xyz>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, DUVAL REMI <REMI(dot)DUVAL(at)cheops(dot)fr>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: proposal: schema variables |
| Date: | 2024-11-16 14:56:53 |
| Message-ID: | 78f3c264-658a-4007-ab79-4cc913fba675@technowledgy.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
Dmitry Dolgov:
> This sounds to me like an argument against allowing name clashing between
> variables and tables. It makes even more sense, since session variables are in
> many ways similar to tables.
+1
My mental model of a session variable is similar to a single-row,
optionally global temporary, table.
Is there any substantial difference that I am not aware of?
Best,
Wolfgang
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2024-11-16 15:36:19 | Re: proposal: schema variables |
| Previous Message | Ranier Vilela | 2024-11-16 14:42:54 | Re: define pg_structiszero(addr, s, r) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2024-11-16 15:36:19 | Re: proposal: schema variables |
| Previous Message | Pavel Stehule | 2024-11-16 14:34:58 | Re: proposal: schema variables |