> 2020年4月9日 下午7:46，tushar <tushar.ahuja@enterprisedb.com> 写道：
>
> On 4/7/20 2:27 PM, 曾文旌 wrote:
>> Vacuum full GTT, cluster GTT is already supported in global_temporary_table_v24-pg13.patch.
>
> Hi Wenjing,
>
> Please refer this scenario , where reindex message is not coming next time ( after reconnecting to database) for
GTT
>
> A)
> --normal table
> postgres=# create table nt(n int primary key);
> CREATE TABLE
> --GTT table
> postgres=# create global temp table gtt(n int primary key);
> CREATE TABLE
> B)
> --Reindex , normal table
> postgres=# REINDEX (VERBOSE) TABLE nt;
> INFO: index "nt_pkey" was reindexed
> DETAIL: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
> REINDEX
> --reindex GTT table
> postgres=# REINDEX (VERBOSE) TABLE gtt;
> INFO: index "gtt_pkey" was reindexed
> DETAIL: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
> REINDEX
> C)
> --Reconnect to database
> postgres=# \c
> You are now connected to database "postgres" as user "tushar".
> D) again perform step B)
>
> postgres=# REINDEX (VERBOSE) TABLE nt;
> INFO: index "nt_pkey" was reindexed
> DETAIL: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
> REINDEX
> postgres=# REINDEX (VERBOSE) TABLE gtt; <-- message not coming
> REINDEX
Yes , Since the newly established connection is on the db, the GTT store file is not initialized, so there is no info
message.
>
> --
> regards,tushar
> EnterpriseDB https://www.enterprisedb.com/
> The Enterprise PostgreSQL Company
