From: Tom Lane <tgl@sss.pgh.pa.us>
To: watts@humbug.antnet.com
Cc: pgsql-hackers@postgreSQL.org
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [HACKERS] Re: [INTERFACES] Revised proposal for libpq and FE/BE protocol changes
Date: Wed, 29 Apr 1998 10:50:28 -0400
Message-ID: <8692.893861428@sss.pgh.pa.us> (raw)
In-Reply-To: <199804282053.PAA21962@humbug.antnet.com>
watts@humbug.antnet.com writes:
> I suggest the application already has fork or fork/exec to
> implement an asynchronous design.
True, if you don't mind assuming you have threads then you could
dedicate one thread to blocking in libpq while your other threads manage
your user interface and so forth. But most of these revisions would
still be useful in that situation. The current libpq does not cope well
with query strings containing multiple commands; it doesn't cope at all
with queries that return more than one type of tuple; it requires dummy
queries (wasting both processing time and network bandwidth) to check
for NOTIFY messages; and so forth. None of those problems can be solved
just by moving calls to libpq into a separate thread.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, watts@humbug.antnet.com, pgsql-hackers@postgreSQL.org
Subject: Re: [HACKERS] Re: [INTERFACES] Revised proposal for libpq and FE/BE protocol changes
In-Reply-To: <8692.893861428@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox