From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Andreas Lubensky <lubensky(at)cognitec(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org >> PG-General Mailing List" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Large objects and savepoints - Snapshot reference leak |
Date: | 2014-01-31 16:39:11 |
Message-ID: | CAFj8pRALcX-1keQRbs6mPH8Q-xKeGohvncJ2ASy5rdhgFQg=ug@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello
This bug was fixed few months by Heikki
Regards
Pavel
Dne 31.1.2014 17:35 "Andreas Lubensky" <lubensky(at)cognitec(dot)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(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2014-01-31 17:19:18 | Re: [HACKERS] Insert result does not match record count |
Previous Message | Andreas Lubensky | 2014-01-31 16:34:28 | Large objects and savepoints - Snapshot reference leak |