Re: Global temporary tables

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Global temporary tables
Date: 2026-06-22 15:30:59
Message-ID: CAFj8pRDbGis5SPwaoGjyeVd9K0ynabEXfe-C3RzOF+d46WLOyA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi

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

>
>
> > On Jun 22, 2026, at 4:57 AM, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
> wrote:
> >
> > On Sun, 21 Jun 2026 at 23:06, Andrew Dunstan <andrew(at)dunslane(dot)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
>
>
>
>
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2026-06-22 15:33:59 Re: Add a greedy join search algorithm to handle large join problems
Previous Message Dilip Kumar 2026-06-22 15:22:01 Re: Proposal: Conflict log history table for Logical Replication