Re: Increasing timeout of poll_query_until for TAP tests - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Increasing timeout of poll_query_until for TAP tests
Date
Msg-id CAB7nPqQnJ7f20ELH_fvWDghBEfR8xhxMQTng2rTg4OE4L_4ZAw@mail.gmail.com
Whole thread Raw
In response to Re: Increasing timeout of poll_query_until for TAP tests  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Increasing timeout of poll_query_until for TAP tests  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
On Thu, Aug 4, 2016 at 2:34 AM, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
> Michael Paquier wrote:
>> On Wed, Aug 3, 2016 at 7:21 AM, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
>
>> > Why not capture both items in a single select, such as in the attached
>> > patch?
>>
>> Let me test this....
>> [... A while after ...]
>> This looks to work properly. 12 runs in a row have passed.
>
> Okay, applied that way.
>
> BTW, one-line long queries look awful in that perl code.  I don't
> propose to change anything now, but I propose that long queries are
> split using here-docs in new code,
>
> $node->safe_psql(<<EQ);
> SELECT foo
>   FROM bar
> EQ

Yep, that would be a good idea. I didn't know this grammar existed. Or
use qq() directly.
-- 
Michael



pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: [sqlsmith] FailedAssertion("!(k == indices_count)", File: "tsvector_op.c", Line: 511)
Next
From: Tom Lane
Date:
Subject: Re: Cache Hash Index meta page.