Search Postgresql Archives

Streaming processing of result sets

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Unless you use COPY, libpq loads the complete query result into
memory.  In some cases, this is not desirable.  I know that with
non-MVCC databases, it is important to load the result from the
database server in a non-blocking fashion because you can easily stall
other transactions or even deadlock if you block during result
processing (waiting for another network connection, for instance).  Is
this true for PostgreSQL as well, or can clients block without causing
too much trouble?

-- 
Florian Weimer                <fweimer@xxxxxx>
BFK edv-consulting GmbH       http://www.bfk.de/
Kriegsstraße 100              tel: +49-721-96201-1
D-76133 Karlsruhe             fax: +49-721-96201-99

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



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux