| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Increasing timeout of poll_query_until for TAP tests |
| Date: | 2016-07-27 01:00:57 |
| Message-ID: | CAB7nPqRqZnXT6XC0e3y0AZ78WxDAytzh9MSFwH-PzEhvpCtOEA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jul 25, 2016 at 10:05 PM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> On Mon, Jul 25, 2016 at 2:52 PM, Michael Paquier
> <michael(dot)paquier(at)gmail(dot)com> wrote:
>> Ah, yes, and that's a stupid mistake. We had better use
>> replay_location instead of write_location. There is a risk that
>> records have not been replayed yet even if they have been written on
>> the standby, so it is possible that the query looking at tab_int may
>> not see this relation.
>
> Or in short, the attached fixes 2) and will help providing input for 1)..
Increasing the timeout had zero effect for test 003:
http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hamster&dt=2016-07-26%2016%3A00%3A07
So we're facing something else. I'll dig into that deeper using
manually hamster.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2016-07-27 01:10:09 | Re: Proposal: revert behavior of IS NULL on row types |
| Previous Message | Andres Freund | 2016-07-27 00:43:33 | Macro customizable hashtable / bitmapscan & aggregation perf |