Re: misleading error message in ProcessUtilitySlow T_CreateStatsStmt
От | Álvaro Herrera |
---|---|
Тема | Re: misleading error message in ProcessUtilitySlow T_CreateStatsStmt |
Дата | |
Msg-id | 202508220946.osn274hnjxez@alvherre.pgsql обсуждение исходный текст |
Ответ на | Re: misleading error message in ProcessUtilitySlow T_CreateStatsStmt (Kirill Reshke <reshkekirill@gmail.com>) |
Ответы |
Re: misleading error message in ProcessUtilitySlow T_CreateStatsStmt
Re: misleading error message in ProcessUtilitySlow T_CreateStatsStmt Re: misleading error message in ProcessUtilitySlow T_CreateStatsStmt |
Список | pgsql-hackers |
On 2025-Aug-21, Kirill Reshke wrote: > I wouldn’t say this is misleading, but " a single relation" is indeed > not precise enough. IMO we need a more precise term to distinguish > regular relation and table func. I'm not sure. See the definition of relation in the glossary: https://www.postgresql.org/docs/18/glossary.html#GLOSSARY-RELATION The generic term for all objects in a database that have a name and a list of attributes defined in a specific order. Tables, sequences, views, foreign tables, materialized views, composite types, and indexes are all relations. More generically, a relation is a set of tuples; for example, the result of a query is also a relation. In PostgreSQL, Class is an archaic synonym for relation. (I wonder why this says "generically" rather than "generally". Is that word choice a mistake?) Maybe in the "For example" clause we can also mention table functions. -- Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
В списке pgsql-hackers по дате отправления: