Re: Using TEMP ON COMMIT DROP, but need logging too.

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Michael Moore <michaeljmoore(at)gmail(dot)com>
Cc: postgres list <pgsql-sql(at)postgresql(dot)org>
Subject: Re: Using TEMP ON COMMIT DROP, but need logging too.
Date: 2016-10-13 21:48:23
Message-ID: CAKFQuwa8CaaPecOJXPWkroUK6G-GnpMF8LDLfXMzq9Sv88vegQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

On Thu, Oct 13, 2016 at 2:24 PM, Michael Moore <michaeljmoore(at)gmail(dot)com>
wrote:

> I've written a function that uses several temporary tables with the ON
> COMMIT DROP option. This function does no updates to the database. Now I
> would like to put in some logging. In otherwords:
>
> insert into my_logging_table values (...);
> commit;
>
> Obviously I can't do the commit without dropping my temp tables.
>
> What is a good way to implement my intended functionality?
>
>
​You can't put "commit" inside a function so I feel like you are failing to
share some important details by not providing code.

David J.

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Michael Moore 2016-10-13 21:53:53 Re: Using TEMP ON COMMIT DROP, but need logging too.
Previous Message Michael Moore 2016-10-13 21:24:19 Using TEMP ON COMMIT DROP, but need logging too.