On Sun, Apr 7, 2013 at 12:54 AM, Jaime Casanova wrote:
> On Sat, Apr 6, 2013 at 11:28 PM, Tom Lane wrote:
>> Jaime Casanova writes:
>>> On Sat, Apr 6, 2013 at 9:16 PM, Tom Lane wrote:
Curious though that we
have not seen this in the buildfarm ...
>>
>>> anyway, your commit fix the pro
On Sat, Apr 6, 2013 at 11:28 PM, Tom Lane wrote:
> Jaime Casanova writes:
>> On Sat, Apr 6, 2013 at 9:16 PM, Tom Lane wrote:
>>> Curious though that we
>>> have not seen this in the buildfarm ...
>
>> anyway, your commit fix the problem. thanks
>
> Thanks for confirming. What platform are you t
Jaime Casanova writes:
> On Sat, Apr 6, 2013 at 9:16 PM, Tom Lane wrote:
>> Curious though that we
>> have not seen this in the buildfarm ...
> anyway, your commit fix the problem. thanks
Thanks for confirming. What platform are you testing on, anyway?
I'm still wondering why you saw it when t
On Sat, Apr 6, 2013 at 9:16 PM, Tom Lane wrote:
> Curious though that we
> have not seen this in the buildfarm ...
anyway, your commit fix the problem. thanks
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
Phone: +593 4 5107566 Cell: +5
Jaime Casanova writes:
> I was running some tests, and noted $SUBJECT.
> It fails consistently on current HEAD (without any patch).
> ...
> Attached regressions.diff, basically the fails give an error of
> "select failed: Interrupted system call"
Hm, looks to me like the select() error path at is
