From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | tgl(at)sss(dot)pgh(dot)pa(dot)us (Tom Lane) |
Cc: | hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Proposal for async support in libpq |
Date: | 1998-04-17 18:00:18 |
Message-ID: | 199804171800.OAA24268@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>
> Here's what I propose to do with libpq to make it more useful for
> real-time applications. Any comments or better ideas?
>
> The point of these changes is first to allow frontend applications to
> receive NOTIFY responses without having to generate dummy queries,
> and second to allow a frontend to perform other work while awaiting
> the result of a query.
>
> We can't break existing code for this, so the behavior of PQexec()
> can't change. Instead, I propose new functions to add to the API.
> Internally, PQexec will be reimplemented in terms of these new
> functions, but old apps won't notice any difference.
This all looks good. Another thing we really need it to be able to
cancel queries. This would be a big win, and looks like it could fit
into the scheme here.
Ideally, I would like to control-c in psql, and have the query cancel,
instead of exiting from pgsql.
--
Bruce Momjian | 830 Blythe Avenue
maillist(at)candle(dot)pha(dot)pa(dot)us | Drexel Hill, Pennsylvania 19026
+ If your life is a hard drive, | (610) 353-9879(w)
+ Christ can be your backup. | (610) 853-3000(h)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 1998-04-17 19:51:17 | Re: [HACKERS] Proposal for async support in libpq |
Previous Message | ocie | 1998-04-17 17:44:43 | Re: [HACKERS] drop table inside transactions |