| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Cc: | Oleksandr Shulgin <oleksandr(dot)shulgin(at)zalando(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pg Bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: PQexec() hangs on OOM |
| Date: | 2015-07-10 13:42:43 |
| Message-ID: | CAB7nPqRgVD+zzG6i7kWqSgkbb5osc7E8eAb3PW3LvCp14G0OSA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, Jul 9, 2015 at 10:04 PM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com>wrote:
> So, here are two patches aimed at fixing the hangling issues with
> getStartCopy and getParamDescriptions. After trying a couple of
> approaches, I found out that the most elegant way to prevent the
> infinite loop in parseInput is to introduce a new PGASYNC flag to
> control the error and let the caller know what happened.
>
> More refactoring could be done, and I think that the use of this new
> ASYNC flag could be spread to other places as well if you think that's
> a useful. For now I have focused only on fixing the existing problems
> with fixes that are rather back-patchable.
>
As those are actually new bug fixes, I am adding an entry in CF 2015-09.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lamontagne, Karlens | 2015-07-10 16:05:21 | Hello i have a request on Postgres PgAdmin 3 client |
| Previous Message | hubert depesz lubaczewski | 2015-07-09 16:54:06 | Re: BUG #13496: INSERT WHERE NOT EXISTS error |