Thanks Alvaro, that is good to know. At the moment we are stuck with
version 9.1.9 and have to stay there at least for Linux. But do I
understand correctly, that the warning can be ignored for the moment?
On Fri, 2014-01-31 at 15:15 -0300, Alvaro Herrera wrote:
Andreas Lubensky wrote:
Hi
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
, 2014-01-23 at 15:07 -0600, Merlin Moncure wrote:
On Thu, Jan 23, 2014 at 8:31 AM, Andreas Lubensky luben...@cognitec.com
wrote:
Hello,
When implementing a database backend with libpq I realized that it seems
to be impossible to declare a cursor on a prepared statement. Is this
correct
Hello,
When implementing a database backend with libpq I realized that it seems
to be impossible to declare a cursor on a prepared statement. Is this
correct? What is the reason for this limitation?
--
with best regards,
Andreas Lubensky
--
Sent via pgsql-general mailing list (pgsql-general
far we use PostgreSQL via ODBC, but now we want to
switch to a native libpq implementation.
--
with best regards,
Andreas Lubensky
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
a
proper replacement (as ODBC probably does) most likely requires a full
blown SQL parser...
On Mon, 2014-01-20 at 14:08 +0400, Dmitriy Igrishin wrote:
Hey Andreas,
2014/1/20 Andreas Lubensky luben...@cognitec.com
Hi,
Is there any way to make PostgreSQL support
Hi,
currently we are trying to integrate Postgres with ODBC and have problems with
blobs.
We tried to use bytea and were under the impression that bytea would act like
a blob in other databases when used through ODBC.
So far we could not make it work properly. It seems we still have to do the
