Search Postgresql Archives

Re: libpq: why only one PQsendQuery per connection at a time?

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

 



sftf-2 wrote
> So question is why this limitaion exists?
> 
> Why PQgetResult(PGconn *conn) operates on connection,
> and not on some unique handler that each "PQsend*" could return.
> 
> Is it limitaion of libpq or architecture of postgresql backend or
> backend-frontend protocol?

IIUC this is a backend Postgres limitation - it was designed in a least
complex way where each process acts in a serial fashion.  A single process
has no way to maintain concurrent state for multiple active queries.

David J.



--
View this message in context: http://postgresql.nabble.com/libpq-why-only-one-PQsendQuery-per-connection-at-a-time-tp5832803p5832807.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.


-- 
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