| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Craig Ringer <craig(at)2ndquadrant(dot)com>, Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com>, Joe Conway <mail(at)joeconway(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: proposal: session server side variables |
| Date: | 2016-12-29 13:25:32 |
| Message-ID: | alpine.DEB.2.20.1612291416170.4911@lancre |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> I newer talked about persistent data. I talked about persistent metadata.
Sure, I finally understood that detail. Now if I hear "persistent
variable", I by default understand that both metadata and data are
persistent... It requires some effort to understand the subtelty.
> I really don't propose any possible substitution of tables (relations).
> I newer did it.
Sure.
> The used terminology is not 100% clean and natural - maybe better name is
> "global temporary unshared untransactional unrelational storage" -
Hmmm. Too long:-) But these properties need to be spelled out.
> [...] I don't see any sense to have two similar storages or two
> redundant access methods - not in PostgreSQL level.
Then say so in the wiki in the cons.
Personnaly, I'm not sure. Maybe having a clean way of declaring a one-row
"singleton" table enforced by postgresql would be enough.
--
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2016-12-29 13:41:17 | Re: proposal: session server side variables |
| Previous Message | Ashutosh Bapat | 2016-12-29 12:44:25 | Re: Assignment of valid collation for SET operations on queries with UNKNOWN types. |