On Mon, Jul 25, 2016 at 10:05 PM, Michael Paquier
<michael.paqu...@gmail.com> wrote:
> On Mon, Jul 25, 2016 at 2:52 PM, Michael Paquier
> <michael.paqu...@gmail.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:
So we're facing something else. I'll dig into that deeper using
manually hamster.

Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:

Reply via email to