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

From Alvaro Herrera
Subject Re: Increasing timeout of poll_query_until for TAP tests
Date
Msg-id 20160803173405.GA636698@alvherre.pgsql
Whole thread Raw
In response to Re: Increasing timeout of poll_query_until for TAP tests  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: Increasing timeout of poll_query_until for TAP tests  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
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

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Andreas Seltenreich
Date:
Subject: [sqlsmith] FailedAssertion("!(k == indices_count)", File: "tsvector_op.c", Line: 511)
Next
From: Joshua Bay
Date:
Subject: Re: Way to access LSN (for each transaction) by directly talking to postgres?