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

From Andreas Lubensky
Subject Large objects and savepoints - Snapshot reference leak
Date
Msg-id 1391186068.21579.7.camel@aries.cognitec-systems.de
Whole thread Raw
Responses Re: Large objects and savepoints - Snapshot reference leak  (Pavel Stehule <pavel.stehule@gmail.com>)
Re: Large objects and savepoints - Snapshot reference leak  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-general
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



pgsql-general by date:

Previous
From: Albe Laurenz
Date:
Subject: Re: Temporary table already exists
Next
From: Pavel Stehule
Date:
Subject: Re: Large objects and savepoints - Snapshot reference leak