The recent Postgres7.4.5 mentions a fix for a crash.
"Repair possible crash during concurrent btree index insertions
This patch fixes a rare case in which concurrent insertions into a btree
index could result in a server panic. No permanent damage would result,
but it's still worth a re-release. The bug does not exist in pre-7.4
Is this crash anyway related to :
WARNING: specified item offset is too large
PANIC: failed to add item to the page for "<table_index_key>"
LOG: server process (PID 3786) was terminated by signal 6
LOG: terminating any other active server processes
I have been getting this crash for a while.
My app uses Postgres 7.4.3 on SunOS 5.9 Generic_112233-01 sun4u sparc
Is it worth to upgrade it to use 7.4.5?
pgsql-novice by date
|Next:||From: Bruce Momjian||Date: 2004-08-30 14:05:01|
|Subject: Re: Release 7.4.5|
|Previous:||From: Tom Lane||Date: 2004-08-30 00:54:20|
|Subject: Re: difference between join syntax |