On Thu, 30 Oct 2003, Jeff Boes wrote:
JB> We are experiencing the following error, usually during our nightly
JB> delete-and-vacuum cycle (when there are very few other connections to
JB> the database):
JB>
JB> 2003-10-30 01:36:59 [25392] LOG: server process (pid 697) was
JB> terminated by signal 14
JB> 2003-10-30 01:36:59 [25392] LOG: terminating any other active server
JB> processes
JB> 2003-10-30 01:37:01 [1977] FATAL: The database system is in recovery mode
JB> 2003-10-30 01:37:08 [25392] LOG: all server processes terminated;
JB> reinitializing shared memory and semaphores
JB> 2003-10-30 01:37:09 [2856] FATAL: The database system is starting up
JB> 2003-10-30 01:37:09 [2855] LOG: database system was interrupted at
JB> 2003-10-30 01:26:13 EST
JB>
JB> The only clues we have are that the server processes interrupted by
JB> "signal 14" *seem* to be backends connected to Apache processes (on
JB> another server). But even that isn't certain, because of the difficulty
JB> in tracking down which process was doing what at the time.
Signal 14 is SIGALRM. Some kind of badly-behaving watchdog?
Sincerely,
D.Marck [DM5020, MCK-RIPE, DM3-RIPN]
------------------------------------------------------------------------
*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- [EMAIL PROTECTED] ***
------------------------------------------------------------------------
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
