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

From: "Dan \"Heron\" Myers" <heron(at)xnapid(dot)com>
To: pgsql-general(at)postgresql(dot)org
Cc: peter(dot)geoghegan86(at)gmail(dot)com, craig(at)postnewspapers(dot)com(dot)au
Subject: Re: Maintaining an index on a large table: Is there any potential for it to stall my application?
Date: 2008-06-03 01:21:11
Message-ID: 48449C87.5050009@xnapid.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Kimball Johnson 2008-06-03 02:41:39 make rows unique across db's without UUIP on windows?
Previous Message Gregory Stark 2008-06-03 01:12:36 Re: turning fsync off for WAL