From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Parallel Append subplan order instability on aye-aye |
Date: | 2019-07-23 23:59:58 |
Message-ID: | CA+hUKGLc1b_uknzYWJbgZnPnip3x-KJmP-M7gVn7Q6=-8cXgRg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Jul 16, 2019 at 12:21 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> In the meantime, we've had *lots* of buildfarm failures in the
> added pg_stat_all_tables query, which indicate that indeed the
> stats collector mechanism isn't terribly reliable. But that
> doesn't directly prove anything about the original problem,
> since the planner doesn't look at stats collector data.
I noticed that if you look at the list of failures of this type, there
are often pairs of animals belonging to Andres that failed at the same
time. I wonder if he might be running a bunch of animals on one
kernel, and need to increase net.core.rmem_max and
net.core.rmem_default (or maybe the write side variants, or both, or
something like that).
--
Thomas Munro
https://enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Steven Pousty | 2019-07-24 00:24:11 | Re: SQL/JSON path issues/questions |
Previous Message | Alvaro Herrera | 2019-07-23 23:57:34 | Re: stress test for parallel workers |