| From: | David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: libpq: why only one PQsendQuery per connection at a time? |
| Date: | 2015-01-04 17:45:38 |
| Message-ID: | 1420393538131-5832807.post@n5.nabble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dmitry Igrishin | 2015-01-04 20:22:43 | Re: libpq: why only one PQsendQuery per connection at a time? |
| Previous Message | sftf-misc | 2015-01-04 16:02:11 | libpq: why only one PQsendQuery per connection at a time? |