Re: [Dovecot] A questions about consume_results (driver-pgsql.c)

2010-03-26 Thread Timo Sirainen
On Thu, 2010-03-25 at 20:04 +0100, Rainer Weikusat wrote: > This is the only part of the driver-pgsql.c code where a > CONNECTION_BAD does not result in driver_pgsql_close being called. > This will likely happen after the next query (from queue or a new one) > failed because the connection was bad.

Re: [Dovecot] A questions about consume_results (driver-pgsql.c)

2010-03-25 Thread Rainer Weikusat
Rainer Weikusat writes: > -- > static void consume_results(struct pgsql_db *db) > { > do { > if (!PQconsumeInput(db->pg)) > break; > > if (PQisBusy(db->pg)) > return; > } while (PQgetResult(db->pg) != N

[Dovecot] A questions about consume_results (driver-pgsql.c)

2010-03-25 Thread Rainer Weikusat
Code -- static void consume_results(struct pgsql_db *db) { do { if (!PQconsumeInput(db->pg)) break; if (PQisBusy(db->pg)) return; } while (PQgetResult(db->pg) != NULL); if (PQstatus