Large objects and savepoints - Snapshot reference leak

From: Andreas Lubensky <lubensky(at)cognitec(dot)com>
To: PostgreSQL General <pgsql-general(at)postgresql(dot)org>
Subject: Large objects and savepoints - Snapshot reference leak
Date: 2014-01-31 16:34:28
Message-ID: 1391186068.21579.7.camel@aries.cognitec-systems.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Pavel Stehule 2014-01-31 16:39:11 Re: Large objects and savepoints - Snapshot reference leak
Previous Message Albe Laurenz 2014-01-31 15:05:00 Re: Temporary table already exists