From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | "Lasher, Glenn" <GLasher(at)nyiso(dot)com> |
Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Difficulty with make check |
Date: | 2009-07-15 13:52:48 |
Message-ID: | 20090715135248.GE4551@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Lasher, Glenn wrote:
> On the QA zone or Production servers, however the same command (adjusted for the number of processors) fails at 'make check' thus:
>
> ---8<-cut----------------------------------------------------------------------
> ./pg_regress --temp-install=./tmp_check --top-builddir=../../.. --srcdir=/usr/us
> ers/postgres/build/postgresql-8.3.7/src/test/regress --temp-port=55432 --schedul
> e=./parallel_schedule --multibyte=SQL_ASCII --load-language=plpgsql
> ============== creating temporary installation ==============
> ============== initializing database system ==============
> ============== starting postmaster ==============
> Killed
> Killed
This seems an environment problem -- process limits set too low or
something like that. It's not related to Postgres itself; it's the
kernel or some layer in between that's disallowing Postgres from running
normally.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Mead | 2009-07-15 15:17:28 | Re: PostgreSQL/PAM problem |
Previous Message | Suvankar Roy | 2009-07-15 10:17:58 | Flush Shared Buffer Cache |