Re: [Proposal] Global temporary tables

Поиск
Список
Период
Сортировка
От 曾文旌
Тема Re: [Proposal] Global temporary tables
Дата
Msg-id 4774529C-B8EA-484A-B34A-1AB6C892B3A0@alibaba-inc.com
обсуждение исходный текст
Ответ на Re: [Proposal] Global temporary tables  (tushar <tushar.ahuja@enterprisedb.com>)
Список pgsql-hackers


2020年4月29日 下午7:46,tushar <tushar.ahuja@enterprisedb.com> 写道:

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.
postgres=# drop index index12;
ERROR:  cannot drop index index12 or global temporary table f
HINT:  Because the index is created on the global temporary table and other backend attached it.

postgres=# drop table f;
ERROR:  cannot drop index index12 or global temporary table f
HINT:  Because the index is created on the global temporary table and other backend attached it.
postgres=#

Dropping an index on a GTT and dropping a GTT with an index can both trigger this message, so the message looks like this, and it feels like there's no better way to do it.



Wenjing




--
regards,tushar
EnterpriseDB  https://www.enterprisedb.com/
The Enterprise PostgreSQL Company

Вложения

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Amit Kapila
Дата:
Сообщение: Re: PG compilation error with Visual Studio 2015/2017/2019
Следующее
От: Ashutosh Bapat
Дата:
Сообщение: Re: [PATCH] Keeps tracking the uniqueness with UniqueKey