| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [COMMITTERS] pgsql: Replication lag tracking for walsenders |
| Date: | 2017-04-22 15:59:37 |
| Message-ID: | 8872.1492876777@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
I wrote:
> Whoa. This just turned into a much larger can of worms than I expected.
> How can it be that processes are getting assertion crashes and yet the
> test framework reports success anyway? That's impossibly
> broken/unacceptable.
Taking a quick census of other buildfarm machines that are known to be
running the recovery test, it appears that most (not all) are seeing
one or both traps. But the test is reporting success anyway, everywhere
except on Noah's 32-bit AIX critters.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-04-22 16:27:35 | Re: [COMMITTERS] pgsql: Replication lag tracking for walsenders |
| Previous Message | Tom Lane | 2017-04-22 15:41:01 | Re: [COMMITTERS] pgsql: Replication lag tracking for walsenders |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-04-22 16:27:35 | Re: [COMMITTERS] pgsql: Replication lag tracking for walsenders |
| Previous Message | Petr Jelinek | 2017-04-22 15:53:19 | Re: walsender & parallelism |