Re: Maintaining an index on a large table: Is there any potential for it to stall my application? - Mailing list pgsql-general

From Dan \"Heron\" Myers
Subject Re: Maintaining an index on a large table: Is there any potential for it to stall my application?
Date
Msg-id 48449C87.5050009@xnapid.com
Whole thread Raw
In response to Re: Maintaining an index on a large table: Is there any potential for it to stall my application?  (Craig Ringer <craig@postnewspapers.com.au>)
List pgsql-general

Craig Ringer wrote:
> Given the choice I'd want to take the async I/O option over threading in
> C++, but I don't get the impression that libpq is really built around
> that model.

libpq has several commands for asynchronous command processing:

http://www.postgresql.org/docs/8.3/static/libpq-async.html

- Dan Myers

pgsql-general by date:

Previous
From: Gregory Stark
Date:
Subject: Re: turning fsync off for WAL
Next
From: Greg Smith
Date:
Subject: Re: turning fsync off for WAL