Downsides of liberally using CREATE TEMP TABLE ... ON COMMIT DROP - Mailing list pgsql-general

From Ryan Murphy
Subject Downsides of liberally using CREATE TEMP TABLE ... ON COMMIT DROP
Date
Msg-id CAHeEsBd5LJfHDkawj9VHfhbtMkrQ-npFw8pyVg2T7mv4=7nkzw@mail.gmail.com
Whole thread Raw
Responses Re: Downsides of liberally using CREATE TEMP TABLE ... ON COMMIT DROP  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-general
Hello,

I heard at a PostgreSQL talk that you should not liberally create temp tables in the course of frequently-used functions etc, because (roughly) you're using up some of the same resources that you for your regular tables.

Is this true?  Is there an important reason not to have e.g. a plpgsql function that uses a temp table?  What are the specific problems if I do this?  Is the problem ameliorated if I add ON COMMIT DROP?

Best,
Ryan

pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: pg 10.1 missing libpq in postgresql-devel
Next
From: "David G. Johnston"
Date:
Subject: Re: Downsides of liberally using CREATE TEMP TABLE ... ON COMMIT DROP