Downsides of liberally using CREATE TEMP TABLE ... ON COMMIT DROP

Поиск
Список
Период
Сортировка
От Ryan Murphy
Тема Downsides of liberally using CREATE TEMP TABLE ... ON COMMIT DROP
Дата
Msg-id CAHeEsBd5LJfHDkawj9VHfhbtMkrQ-npFw8pyVg2T7mv4=7nkzw@mail.gmail.com
обсуждение исходный текст
Ответы Re: Downsides of liberally using CREATE TEMP TABLE ... ON COMMIT DROP  ("David G. Johnston" <david.g.johnston@gmail.com>)
Список 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 по дате отправления:

Предыдущее
От: Adrian Klaver
Дата:
Сообщение: Re: pg 10.1 missing libpq in postgresql-devel
Следующее
От: "David G. Johnston"
Дата:
Сообщение: Re: Downsides of liberally using CREATE TEMP TABLE ... ON COMMIT DROP