Please note that everyone here but you is bottom-posting; please follow the convention and list standard. Susan Cassidy-3 wrote > It is never committed, because the lookup for the insert fails. So, alter the code so only the first insert happens then stop further processing and go explore that state of the database. Or, add a "commit" after the initial insert so at least that is memorialized for future research even if the rest of the code fails. You are going to have to do some leg-work here; a pure thought experiment is not going to cut it. David J. -- View this message in context: http://postgresql.1045698.n5.nabble.com/any-way-for-a-transaction-to-see-inserts-done-earlier-in-the-transaction-tp5800432p5800567.html Sent from the PostgreSQL - general mailing list archive at Nabble.com. -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
