Re: Performance issue on temporary relations

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: 章晨曦 <zhangchenxi(at)halodbtech(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Performance issue on temporary relations
Date: 2025-08-19 15:55:41
Message-ID: CAKFQuwYd-2bTd_nENYMTfmKbpX8BCAKBBf9UGsvEzujZM7CGxg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Aug 19, 2025 at 8:45 AM 章晨曦 <zhangchenxi(at)halodbtech(dot)com> wrote:

> > I do not think this is something we ought to consider. It might help
> > certain corner use-cases, but it's probably a net loss for most.
> > In particular, I don't think that creating thousands of temp tables in
> > a session but then touching only a few of them in any one transaction
> > is a very plausible usage pattern.
>
> Acturely, we just facing such problem in some real systems. More than 3,700
> temporary tables created! I accept such case is not that common, but it
> does exist.
>
>
It is unfair to add a performance penalty to everyone just because some
people write bad code. I concur that adding complexity to the system to
gracefully handle this corner-case doesn't seem justified. A use case
description, not mere existence, is needed to provide such justification.

David J.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-08-19 15:56:41 Re: When deleting the plpgsql function, release the CachedPlan of the function
Previous Message Filip Janus 2025-08-19 15:48:31 Re: Proposal: Adding compression of temporary files