I don't think Dan's problem is related to the recently found VACUUM
bugs. Killing a backend with SIGVTALRM suggests that something thinks
the backend's been running too long. ulimit is a likely suspect.
Another possibility is some sort of profiling mechanism gone haywire.
There's nothing in our
Dan Moschuk <[EMAIL PROTECTED]> writes:
> | > Server process (pid 13361) exited with status 26 at Fri Nov 3 17:49:44 2000
> |
> | What's signal 26 on your system?
> #define SIGVTALRM 26 /* virtual time alarm */
Well, that sure shouldn't be happening. You aren't perhaps running it
u
* Dan Moschuk <[EMAIL PROTECTED]> [001103 15:32] wrote:
>
> | > This happens fairly regularly. I assume exit code 26 is used to dictate
> | > that a specific error has occured.
> | >
> | > The database is a decent size (~3M records) with about 4 indexes.
> |
> | What version of postgresql? To
| > This happens fairly regularly. I assume exit code 26 is used to dictate
| > that a specific error has occured.
| >
| > The database is a decent size (~3M records) with about 4 indexes.
|
| What version of postgresql? Tom Lane recently fixed some severe problems
| with vacuum and heavily u
| > Server process (pid 13361) exited with status 26 at Fri Nov 3 17:49:44 2000
|
| What's signal 26 on your system? (Look in /usr/include/signal.h or
| /usr/include/signum.h or /usr/include/sys/signal.h)
dan@spirit:/home/dan grep 26 /usr/include/sys/signal.h
#define SIGVTALRM 26 /
Dan Moschuk <[EMAIL PROTECTED]> writes:
> Server process (pid 13361) exited with status 26 at Fri Nov 3 17:49:44 2000
What's signal 26 on your system? (Look in /usr/include/signal.h or
/usr/include/signum.h or /usr/include/sys/signal.h)
regards, tom lane
* Dan Moschuk <[EMAIL PROTECTED]> [001103 14:55] wrote:
>
> Server process (pid 13361) exited with status 26 at Fri Nov 3 17:49:44 2000
> Terminating any active server processes...
> NOTICE: Message from PostgreSQL backend:
> The Postmaster has informed me that some other backend died a
Server process (pid 13361) exited with status 26 at Fri Nov 3 17:49:44 2000
Terminating any active server processes...
NOTICE: Message from PostgreSQL backend:
The Postmaster has informed me that some other backend died abnormally and
possibly corrupted shared memory.
I have ro
