Re: Global temporary tables

From: Gilles Darold <gilles(at)darold(dot)net>
To: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Global temporary tables
Date: 2026-06-24 04:15:21
Message-ID: 1a08e269-efec-4a64-a4a0-57135669f60f@darold.net
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Le 24/06/2026 à 06:34, Dean Rasheed a écrit :
> On Tue, 23 Jun 2026 at 10:12, Dean Rasheed<dean(dot)a(dot)rasheed(at)gmail(dot)com> wrote:
>> v3 attached, attempting to fix another issue reported by the cfbot --
>> need to tolerate relation_open() on a global temporary relation, when
>> in parallel mode because pg_get_viewdef() does that.
> Ugh, that still wasn't quite right. Here's v4 with more fixes for
> parallel workers.
>
> Regards,
> Dean

Congratulations, it's an ingenious implementation. Aside from
portability with other DBMSs, the fundamental advantage of GTTs is
avoiding catalog fragmentation caused by the intensive use of temporary
tables. This is what the patch looks to achieve.

I will try to do more checks.

Best regards.

--
Gilles Darold
http://hexacluster.ai/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2026-06-24 04:17:55 Re: Improve pg_stat_statements scalability
Previous Message Michael Paquier 2026-06-24 04:12:09 Re: Add pg_stat_kind_info system view