| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, davec(at)postgresintl(dot)com, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Subject: | Re: orangutan seizes up during isolation-check |
| Date: | 2015-01-15 06:04:28 |
| Message-ID: | 20150115060428.GB2891793@tornado.leadboat.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jan 14, 2015 at 04:48:53PM -0500, Peter Eisentraut wrote:
> What I'm seeing now is that the unaccent regression tests when run under
> make check-world abort with
>
> FATAL: postmaster became multithreaded during startup
> HINT: Set the LC_ALL environment variable to a valid locale.
contrib/unaccent/Makefile sets NO_LOCALE=1, so that makes sense. I expect the
patch over here will fix it:
http://www.postgresql.org/message-id/20150109063015.GA2491320@tornado.leadboat.com
> The behavior is also a bit strange. The step
>
> ============== starting postmaster ==============
>
> hangs for one minute before failing. This probably has nothing to do
> with your change, but maybe pg_regress could detect postmaster startup
> failures better.
Yeah, I think any postmaster startup failure has that effect. Not ideal.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro HORIGUCHI | 2015-01-15 06:05:08 | Re: Overhauling our interrupt handling |
| Previous Message | Amit Kapila | 2015-01-15 05:55:08 | Re: Parallel Seq Scan |