From: | mephysto <mephystoonhell(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Temporary table already exists |
Date: | 2014-01-31 10:20:32 |
Message-ID: | 1391163632428-5789852.post@n5.nabble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi there,
in my database I'm using several stored_functions that take advantage of
temporary table. The application that is connected to Postgres is a Java Web
Application in a Glassfish Application Server: it is connected by a JDBC
Connection Pool provided by Glassfish with this settings:
Resource type -> javax.sql.ConnectionPoolDataSouce
Dataset Classname -> org.postgresql.ds.PGConnectionPoolDataSource
Transaction Isolation -> read-uncommitted
The problem is that in a concurrent execution of a function, I received
error of relation already exists. The relation that caused issue is exactly
my temporary table.
My question is: what is the reason for which I take this type of error? Is
there a way to follow to avoid this situation?
Thanks in advance.
Mephysto
--
View this message in context: http://postgresql.1045698.n5.nabble.com/Temporary-table-already-exists-tp5789852.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
From | Date | Subject | |
---|---|---|---|
Next Message | alexandros_e | 2014-01-31 10:25:09 | Re: Reindexing and tablespaces |
Previous Message | Michael Paquier | 2014-01-31 04:49:43 | Re: Reindexing and tablespaces |