| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Konstantin Knizhnik <knizhnik(at)garret(dot)ru> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: global temporary table (GTT) - are there some ideas how to implement it? |
| Date: | 2026-01-12 06:57:39 |
| Message-ID: | CAFj8pRDpWgQ3=eR037O1GrocqTrTBFxiBuk4_zQf_hCK+K4xaw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chao Li | 2026-01-12 07:08:21 | Re: pg_recvlogical: Prevent flushed data from being re-sent after restarting replication |
| Previous Message | Xuneng Zhou | 2026-01-12 06:53:46 | Re: Implement waiting for wal lsn replay: reloaded |