Re: Re: any way for a transaction to "see" inserts done earlier in the transaction?

From: Vincent Veyron <vv(dot)lists(at)wanadoo(dot)fr>
To: Susan Cassidy <susan(dot)cassidy(at)decisionsciencescorp(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Re: any way for a transaction to "see" inserts done earlier in the transaction?
Date: 2014-04-17 17:40:43
Message-ID: 20140417194043.57411779c6bdc907f603f135@wanadoo.fr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, 17 Apr 2014 10:02:00 -0700
Susan Cassidy <susan(dot)cassidy(at)decisionsciencescorp(dot)com> wrote:

> I moved the code in the function inline into the code, and I still cannot
> find the newly inserted id the next time through the loop.

I suppose you use DBD::Pg, whose current default isolation transaction level is ``Serializable''

Don't know if it applies, but the Postgresql's documentation says this :

SERIALIZABLE

All statements of the current transaction can only see rows committed before the first query or data-modification statement was executed in this transaction. If a pattern of reads and writes among concurrent serializable transactions would create a situation which could not have occurred for any serial (one-at-a-time) execution of those transactions, one of them will be rolled back with a serialization_failure SQLSTATE.

--
Regards, Vincent Veyron

http://libremen.com/
Legal case, contract and insurance claim management software

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Steve Spence 2014-04-17 17:43:43 Re: Arduino SQL Connector
Previous Message Vincent Veyron 2014-04-17 17:38:44 Re: Re: any way for a transaction to "see" inserts done earlier in the transaction?