Re: global temporary table (GTT) - are there some ideas how to implement it? - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: global temporary table (GTT) - are there some ideas how to implement it?
Date
Msg-id CAFj8pRDpWgQ3=eR037O1GrocqTrTBFxiBuk4_zQf_hCK+K4xaw@mail.gmail.com
Whole thread Raw
In response to Re: global temporary table (GTT) - are there some ideas how to implement it?  (Konstantin Knizhnik <knizhnik@garret.ru>)
Responses Re: global temporary table (GTT) - are there some ideas how to implement it?
List pgsql-hackers
Hi
 

I do not completely understand how partitioning of system tables can
solve this problem.
Do you propose that each backend has its own (private) partition?
It seems to be impossible and can cause even worse catalog bloating
(instead of  one temp table we will have to create temp partitions for
multiple system tables).

yes - but what is important - each backend has its own global temp partitions. Then almost all metadata will be static and only statistic related will be temporary.

The backend related partitions have to be of global temp table, not local temp table (only then it makes sense).

The main target is removing bloat from the system catalog, and it is impossible without storing system data to GTT.




 

pgsql-hackers by date:

Previous
From: Xuneng Zhou
Date:
Subject: Re: Implement waiting for wal lsn replay: reloaded
Next
From: Chao Li
Date:
Subject: Re: pg_recvlogical: Prevent flushed data from being re-sent after restarting replication