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

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Rob Sargent <robjsargent(at)gmail(dot)com>
Cc: Andy Colson <andy(at)squeakycode(dot)net>, Ryan Murphy <ryanfmurphy(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Downsides of liberally using CREATE TEMP TABLE ... ON COMMIT DROP
Date: 2018-01-28 21:45:31
Message-ID: CAKFQuwakSzOiejcLqTdFO_sUizF7LYguWO=r3RWN7zDC=hGBbg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sunday, January 28, 2018, Rob Sargent <robjsargent(at)gmail(dot)com> wrote:
>
> The commit in question is the function btw.
>

That doesn't make sense - functions can't commit.

David J.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Thiemo Kellner 2018-01-28 22:24:47 Re: FW: Setting up streaming replication problems
Previous Message Igal @ Lucee.org 2018-01-28 20:49:31 Re: pg_trgm Extension Installed but Operators and Functions do not exist