Re: Global temporary tables - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: Global temporary tables
Date
Msg-id CAFj8pRDbGis5SPwaoGjyeVd9K0ynabEXfe-C3RzOF+d46WLOyA@mail.gmail.com
Whole thread
In response to Re: Global temporary tables  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Hi

po 22. 6. 2026 v 15:43 odesílatel Andrew Dunstan <andrew@dunslane.net> napsal:


> On Jun 22, 2026, at 4:57 AM, Dean Rasheed <dean.a.rasheed@gmail.com> wrote:
>
> On Sun, 21 Jun 2026 at 23:06, Andrew Dunstan <andrew@dunslane.net> wrote:
>>
>> Wow, we're on the same track. I have a patch series for exactly this
>> feature that I was about to submit.
>>
>> FTR here's where I'm at. I'll try to take a look at yours ASAP.
>
> Oh, wow. There's a lot of similarity between our patchsets, which is
> reassuring, but there are also a number of differences, which I need
> to think about in more detail.

Yeah, agree on both fronts. The main areas I see are the catalog and handling wraparound. I don’t think there’s necessarily a clear winner on either, so I’ll be interested to hear what others say.

next week I'll have free time, I can check these patches

generally - global temporary tables is super useful for migration from other systems

Regards

Pavel
  

Cheers

Andrew




pgsql-hackers by date:

Previous
From: Dilip Kumar
Date:
Subject: Re: Proposal: Conflict log history table for Logical Replication
Next
From: Tomas Vondra
Date:
Subject: Re: Add a greedy join search algorithm to handle large join problems