> 2020年4月8日 下午6:34，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.
> Please refer this below scenario , where pg_upgrade is failing
> 1)Server is up and running (./pg_ctl -D data status)
> 2)Stop the server ( ./pg_ctl -D data stop)
> 3)Connect to server using single user mode ( ./postgres --single -D data postgres) and create a global temp table
> [tushar@localhost bin]$ ./postgres --single -D data1233 postgres
>
> PostgreSQL stand-alone backend 13devel
> backend> create global temp table t(n int);
>
> --Press Ctl+D to exit
>
> 4)Perform initdb ( ./initdb -D data123)
> 5.Run pg_upgrade
> [tushar@localhost bin]$ ./pg_upgrade -d data -D data123 -b . -B .
> --
> --
> --
> Restoring database schemas in the new cluster
> postgres
> *failure*
> Consult the last few lines of "pg_upgrade_dump_13592.log" for
> the probable cause of the failure.
> Failure, exiting
>
> log file content -
>
> [tushar@localhost bin]$ tail -20 pg_upgrade_dump_13592.log
> pg_restore: error: could not execute query: ERROR: pg_type array OID value not set when in binary upgrade mode
I found that the regular table also has this problem, I am very unfamiliar with this part, so I opened another email to
consultthis problem.
> Command was:
> -- For binary upgrade, must preserve pg_type oid
> SELECT pg_catalog.binary_upgrade_set_next_pg_type_oid('13594'::pg_catalog.oid);
>
>
> -- For binary upgrade, must preserve pg_class oids
> SELECT pg_catalog.binary_upgrade_set_next_heap_pg_class_oid('13593'::pg_catalog.oid);
>
> CREATE GLOBAL TEMPORARY TABLE "public"."t" (
> "n" integer
> )
> WITH ("on_commit_delete_rows"='false');
>
> -- For binary upgrade, set heap's relfrozenxid and relminmxid
> UPDATE pg_catalog.pg_class
> SET relfrozenxid = '0', relminmxid = '0'
> WHERE oid = '"public"."t"'::pg_catalog.regclass;
>
> --
> regards,tushar
> EnterpriseDB https://www.enterprisedb.com/
> The Enterprise PostgreSQL Company
