Postgres Pro
Downloads
Home   >   mailing lists

Using TEMP ON COMMIT DROP, but need logging too. - Mailing list pgsql-sql

From Michael Moore
Subject Using TEMP ON COMMIT DROP, but need logging too.
Date
Msg-id CACpWLjNTwfGmx+atGRRC0yuwmiRAkHYr-sorzM1-Xrt5Kyd2OQ@mail.gmail.com
Whole thread Raw
Responses Re: Using TEMP ON COMMIT DROP, but need logging too.  ("David G. Johnston" <david.g.johnston@gmail.com>)
Re: Using TEMP ON COMMIT DROP, but need logging too.  (Benjamin Dietrich <b.dietrich@uni-tuebingen.de>)
List pgsql-sql
Tree view
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?

Thanks, Mike


pgsql-sql by date:

Previous
From: Adelo Herrero Pérez
Date:
Subject: Re: How to get the position of each record in a SELECT statement
Next
From: "David G. Johnston"
Date:
Subject: Re: Using TEMP ON COMMIT DROP, but need logging too.