From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Justin Clift <jclift(at)iprimus(dot)com(dot)au> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Alexander Klimov <ask(at)wisdom(dot)weizmann(dot)ac(dot)il>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Tests randomly failed |
Date: | 2001-03-22 23:27:01 |
Message-ID: | 14356.985303621@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Justin Clift <jclift(at)iprimus(dot)com(dot)au> writes:
> If it's of any help, I get the same types of regression testing failures
> on Solaris, with the same "is the backend running?" type error
> messages.. when the installation of solaris HAS NOT had it's /etc/system
> file altered to change the amount of shared memory segments and
> semaphores.
> Whenever I have those problems, I insert the updated (higher) values for
> shared memory and semaphores, reboot the system, then the tests pass as
> the backend is able to start fine.
Hm. That's interesting, but it's fairly hard to believe. For at least
a couple releases past, Postgres has grabbed all the shared memory and
semaphores that it wants at postmaster start. Insufficient shmem/sema
resources should result in postmaster abort, not in occasional failures
to start backends.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Clift | 2001-03-22 23:55:07 | Re: Tests randomly failed |
Previous Message | Justin Clift | 2001-03-22 22:24:33 | Re: Tests randomly failed |