Title: backend died
Our customer running Postgres v. 7.3.2 reported a problem, occurring
couple times a week on three different servers, all on Solaris 9.
We enabled debugging in postgresql.conf, now it happened again;
here's the excerpt from the database log:
2004-11-13 10:01:06 [10456]
Brusser, Michael [EMAIL PROTECTED] writes:
Our customer running Postgres v. 7.3.2 reported a problem, occurring
couple times a week on three different servers, all on Solaris 9.
2004-11-13 10:01:06 [10456] DEBUG: child process (pid 19285) was
terminated by signal 10
SIGBUS iirc.
What
Title: RE: [HACKERS] backend died
Brusser, Michael [EMAIL PROTECTED] writes:
Our customer running Postgres v. 7.3.2 reported a problem, occurring
couple times a week on three different servers, all on Solaris 9.
2004-11-13 10:01:06 [10456] DEBUG: child process (pid 19285
Brusser, Michael [EMAIL PROTECTED] writes:
2004-11-13 10:01:06 [10456] DEBUG: child process (pid 19285) was
terminated by signal 10
The log-statements option was already enabled,
here's what I see prior to the crash:
That's no help. What were the last few lines from process 19285?
This
Title: RE: [HACKERS] backend died
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]]
Sent: Monday, November 15, 2004 3:34 PM
To: Brusser, Michael
Cc: Pgsql-Hackers (E-mail)
Subject: Re: [HACKERS] backend died
Brusser, Michael [EMAIL PROTECTED] writes:
2004-11
Brusser, Michael [EMAIL PROTECTED] writes:
That's no help. What were the last few lines from process 19285?
there are no prior occurrences of token 19285 in the file.
Hmm, so it seems 19285 died during startup. That does make a hardware
problem seem a bit plausible --- the backend start
Hello all,
sometimes I have got a problem with one of my tables.
It has got 25 columns, one unique key and an additional index.
There are about 368.000 rows in this particular table.
Sometimes after running for several days the table is corrupted.
If the tablename is tablename and the
Henrik Steffen [EMAIL PROTECTED] writes:
sometimes I have got a problem with one of my tables.
If you are getting a backend coredump, please provide a stack backtrace.
regards, tom lane
---(end of broadcast)---
TIP 5:
