| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Andre Oliveira Freitas <afreitas(at)callixbrasil(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: PQConsumeinput stuck on recv |
| Date: | 2018-03-05 21:01:48 |
| Message-ID: | 20180305210148.b3cydctauayprxlv@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi,
On 2018-03-05 17:57:51 -0300, Andre Oliveira Freitas wrote:
> Ok, on one hand glad to hear that is an artifact, on the other hand
> that means the issue is still out there...
>
> I'm not a maintainer of Freeswitch, I am an user of it. However I am
> trying to supply the maintainers with any relevant information
> regarding this issue.
>
> As you mentioned, I see the socket being modified and passed around in
> the source code. Do you think the implementation is OK? I do not know
> if that's standard practice when consuming libpq.
It's ok to pass the socket around, it'd not be ok to change whether the
socket blocks or not. I don't have the time to review the freeswitch
code to see whether it does so.
- Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tim Cross | 2018-03-05 21:10:07 | Re: Best options for new PG instance |
| Previous Message | Andre Oliveira Freitas | 2018-03-05 20:57:51 | Re: PQConsumeinput stuck on recv |