Re: libpq connection status and closed fd
| От | Dmitriy Igrishin |
|---|---|
| Тема | Re: libpq connection status and closed fd |
| Дата | |
| Msg-id | CAAfz9KPjVLi+i9x=C-YYQ5zakZcJfJRdERQnmVpgXB5_4Fg-dw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: libpq connection status and closed fd (Marko Tiikkaja <marko@joh.to>) |
| Список | pgsql-hackers |
2014-09-22 12:36 GMT+04:00 Marko Tiikkaja <marko@joh.to>:
On 9/22/14 9:45 AM, Dmitriy Igrishin wrote:2014-09-22 11:35 GMT+04:00 Daniele Varrazzo <daniele.varrazzo@gmail.com>:On Mon, Sep 22, 2014 at 8:17 AM, Dmitriy Igrishin <dmitigr@gmail.com>I read it. You are testing for an error, but use libpq in a wrong way in
wrote:Why are you using close() instead of PQfinish()?
Because I'm testing for an error, please read my message and the
original bug report.
your test case. You must use PQfinish() to close the connection
and PQstatus() will works for you.
Perhaps you should go back and re-read it then. The point of the test case is not to test connection closure; it's to test behaviour in the presence of network errors.
And where the network error emulation in the test case? By closing fd?
I'm sorry if I don't understand something, but really, I don't see any problem
or incorrect behavior of *libpq*. It's behavior adequate to a test case.
.marko
// Dmitriy.
В списке pgsql-hackers по дате отправления: