Re: PQexec() hangs on OOM
| От | Michael Paquier |
|---|---|
| Тема | Re: PQexec() hangs on OOM |
| Дата | |
| Msg-id | CAB7nPqSb3RF=s+BDyq1Un2+rng20EQQyxajdTRtpRG7XsyuLnw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: PQexec() hangs on OOM (Michael Paquier <michael.paquier@gmail.com>) |
| Ответы |
Re: PQexec() hangs on OOM
|
| Список | pgsql-bugs |
On Mon, Apr 6, 2015 at 3:54 PM, Michael Paquier <michael.paquier@gmail.com> wrote: > In this case, as what happens is an OOM related to the allocation of > PGResult, I think that we had better store a status flag in PGConn related > to this OOM, as PGConn->errorMessage may not be empty to take care of the > ambiguity that PGResult == NULL does not necessarily mean wait for more > results. Something like PGResultStatus to avoid any API incompatibility. > Thoughts? > Second idea: return a status with parseInput as it is not part of the APIs of libpq. -- Michael
В списке pgsql-bugs по дате отправления: