Re: [Proposal] Global temporary tables
От | tushar |
---|---|
Тема | Re: [Proposal] Global temporary tables |
Дата | |
Msg-id | 2fad3742-6062-9ee6-10b8-198fa23027a0@enterprisedb.com обсуждение исходный текст |
Ответ на | Re: [Proposal] Global temporary tables (曾文旌 <wenjing.zwj@alibaba-inc.com>) |
Ответы |
Re: [Proposal] Global temporary tables
|
Список | pgsql-hackers |
On 4/29/20 8:52 AM, 曾文旌 wrote: > Fixed the error message to make the expression more accurate. In v33. Thanks wenjing Please refer this scenario , where getting an error while performing cluster o/p 1) X terminal - postgres=# create global temp table f(n int); CREATE TABLE Y Terminal - postgres=# create index index12 on f(n); CREATE INDEX postgres=# \q X terminal - postgres=# reindex index index12; REINDEX postgres=# cluster f using index12; ERROR: cannot cluster on invalid index "index12" postgres=# drop index index12; DROP INDEX if this is an expected , could we try to make the error message more simpler, if possible. Another issue - X terminal - postgres=# create global temp table f11(n int); CREATE TABLE postgres=# create index ind1 on f11(n); CREATE INDEX postgres=# create index ind2 on f11(n); CREATE INDEX postgres=# Y terminal - postgres=# drop table f11; ERROR: cannot drop index ind2 or global temporary table f11 HINT: Because the index is created on the global temporary table and other backend attached it. postgres=# it is only mentioning about ind2 index but what about ind1 and what if - they have lots of indexes ? i think - we should not mix index information while dropping the table and vice versa. -- regards,tushar EnterpriseDB https://www.enterprisedb.com/ The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: