Skip site navigation (1) Skip section navigation (2)

Re: asynchronous execution

From: tomas(at)nocrew(dot)org (=?iso-8859-1?q?Tomas_Sk=E4re?=)
To: "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com>
Cc: <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: asynchronous execution
Date: 2005-11-23 07:54:11
Message-ID: 80veyjvly4.fsf@junk.nocrew.org (view raw or flat)
Thread:
Lists: pgsql-odbc
"Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> writes:

>> Are there any work done, or plans for implementing asynchronous
>> execution in psqlodbc?
>
> Not sure about future plans, but there is nothing stopping you from
> opening thread in your app and running odbc call that way.

It's not that easy, because the application is using libraries that
are not threadsafe, and I thought it would be best to use ODBC async
functionality, if it's available. Separating just the ODBC calls in
another thread would be too much trouble. 

>> Does libpq support asynchronous calls?
>
> yes:
> http://www.postgresql.org/docs/8.1/interactive/libpq-async.html
>
> If you have deep requirements and/or are extremely speed concerned
> (and are not concerned about portability), you may want to make direct
> use of liqpq api.

That's also not an option, since we'd like to have the possibility of
choosing another DBMS.

Oh well, I'll live with blocking functions right now, and if we really
need it, I guess I'll have to try to implement it into psqlodbc.


Tomas

In response to

pgsql-odbc by date

Next:From: Dave PageDate: 2005-11-23 08:59:59
Subject: Re: Continuing encoding fun....
Previous:From: mikeDate: 2005-11-23 05:26:33
Subject: System Error 998

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group