Re: Large objects and savepoints - Snapshot reference leak - Mailing list pgsql-general

From Pavel Stehule
Subject Re: Large objects and savepoints - Snapshot reference leak
Date
Msg-id CAFj8pRALcX-1keQRbs6mPH8Q-xKeGohvncJ2ASy5rdhgFQg=ug@mail.gmail.com
Whole thread Raw
In response to Large objects and savepoints - Snapshot reference leak  (Andreas Lubensky <lubensky@cognitec.com>)
List pgsql-general

Hello

This bug was fixed few months by Heikki

Regards

Pavel

Dne 31.1.2014 17:35 "Andreas Lubensky" <lubensky@cognitec.com> napsal(a):
Hi,

I'm trying to read/write large objects via libpq. I encapsulated the
operations in a transaction but I wanted to put a savepoint before doing
any operations, so I can do a rollback in case anything fails without
breaking the current transaction. Now, when sth. actually fails and the
transaction is rolled back to the savepoint, the next commit results in
a warning:
Snapshot reference leak: Snapshot 0xb5e4b0 still referenced
I'm not sure what to make of that. Can it be ignored? Is rolling back
large object operations not possible?

--
with best regards,

Andreas Lubensky

Software Engineer



--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

pgsql-general by date:

Previous
From: Andreas Lubensky
Date:
Subject: Large objects and savepoints - Snapshot reference leak
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Insert result does not match record count