| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: cygwin64 assertion failure |
| Date: | 2016-10-10 14:54:29 |
| Message-ID: | 32429.1476111269@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> writes:
> On Sun, Oct 9, 2016 at 10:23 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>> lorikeet seems to be stuck running the parallel tests, after having failed
>> an assertion.
> It looks like this problem has been discussed before [1]. Shall we do
> what Tom has suggested there?
> [1] - https://www.postgresql.org/message-id/15344.1473974558%40sss.pgh.pa.us
Well, we now have *two* issues. One is why is the Assert failing.
The other is why is the system failing to clean up afterwards --- you'd
expect that an Assert in a parallel worker would not be a case that the
developers never saw ;-). I'd suggest fixing the latter first.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Francisco Olarte | 2016-10-10 15:03:56 | Re: vacuumdb -f and -j options (was Question / requests.) |
| Previous Message | Merlin Moncure | 2016-10-10 14:44:57 | Re: autonomous transactions |