It is never committed, because the lookup for the insert fails. Susan
On Wed, Apr 16, 2014 at 5:39 PM, David G Johnston < david.g.johns...@gmail.com> wrote: > Susan Cassidy-3 wrote > > Nor can any regular SELECTs in the main program find it. > > Ever? > > If this is a same transaction visibility issue then when your Perl program > stops you should be able to go find that ID manually to confirm it was > inserted and committed properly. If you still cannot find the ID then this > whole line of exploration (i.e., same session visibility) is pointless > since > we know beyond doubt committed data is visible to all other sessions. > > This would also further support the mistaken object identity theory I > proposed up-thread. > > 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-tp5800432p5800463.html > Sent from the PostgreSQL - general mailing list archive at Nabble.com. > > > -- > Sent via pgsql-general mailing list (pgsql-general@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-general >
