Re: [HACKERS] proposal: session server side variables
От | Fabien COELHO |
---|---|
Тема | Re: [HACKERS] proposal: session server side variables |
Дата | |
Msg-id | alpine.DEB.2.20.1612292018040.32017@lancre обсуждение исходный текст |
Ответ на | Re: [HACKERS] proposal: session server side variables (Pavel Stehule <pavel.stehule@gmail.com>) |
Ответы |
Re: [HACKERS] proposal: session server side variables
Re: [HACKERS] proposal: session server side variables |
Список | pgsql-hackers |
> There is a singleton table :) > > create table foo(x integer unique not null default 1 check(x = 1), y integer); > insert into foo(y) values(100); > analyze foo; I know this one. It can be empty, which a singleton cannot be. For a singleton table, you should have one and only one row, you cannot insert or delete, so this is only part of the real thing. > For example - MySQL @var is volatile - can be changed in query - that's > mean, you cannot use it as const for planner :( Indeed, because of the ":=" within in a SELECT query, the variable is updated at each round. Yuk. -- Fabien.
В списке pgsql-hackers по дате отправления: