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

From: Rob Sargent <robjsargent(at)gmail(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(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-29 06:02:40
Message-ID: 130628A4-A3E1-4CFC-A704-653A587B818B@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I think the table is dropped by end of function

> On Jan 28, 2018, at 2:45 PM, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
>> 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

Browse pgsql-general by date

  From Date Subject
Next Message Bjørn T Johansen 2018-01-29 07:47:51 Re: pgaudit for PostgreSQL 10?
Previous Message Igal @ Lucee.org 2018-01-29 05:56:26 Consider Spaces in pg_trgm for Better Similarity