BUG #8345: PostGre SQL database is crashing
The following bug has been logged on the website:
Bug reference: 8345
Logged by: Arun Kumar
Email address: arun.rh@gmail.com
PostgreSQL version: Unsupported/Unknown
Operating system: Linux kernel 2.6.29
Description:
Currently we have ported PostGRE SQL database on to the Linux kernel 2.6.29
with Motorolla coldfire cross platform.
Version of PostgreSQL = 7.4.3.
Problem is when multiple threads are accessing the postgresql database some
times it is seen that, the database is getting crashed. Also we have seen
the following error displayed:
WARNING: terminating connection because of crash of another server process.
DETAIL: The postmaster has commanded this server process to roll back
current transaction and exit, because another server process exited
abnormally and possibly corrupted the shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat
your command.
Some times it wont recover the database.
Let me know what could be the issue and what fix is required.
Regards
Arun R.H
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Hello
2013/7/30 <arun.rh@gmail.com>:
The following bug has been logged on the website:
Bug reference: 8345
Logged by: Arun Kumar
Email address: arun.rh@gmail.com
PostgreSQL version: Unsupported/Unknown
Operating system: Linux kernel 2.6.29
Description:Currently we have ported PostGRE SQL database on to the Linux kernel 2.6.29
with Motorolla coldfire cross platform.
Version of PostgreSQL = 7.4.3.
This version is very old, and there are exists lot of upgrade of
7.4.3, so please upgrade to last 7.4 version
http://www.postgresql.org/ftp/source/v7.4.30/ is probably last.
Regards
Pavel Stehule
Problem is when multiple threads are accessing the postgresql database some
times it is seen that, the database is getting crashed. Also we have seen
the following error displayed:WARNING: terminating connection because of crash of another server process.
DETAIL: The postmaster has commanded this server process to roll back
current transaction and exit, because another server process exited
abnormally and possibly corrupted the shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat
your command.Some times it wont recover the database.
Let me know what could be the issue and what fix is required.Regards
Arun R.H--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On Wed, Jul 31, 2013 at 2:12 AM, Pavel Stehule <pavel.stehule@gmail.com>wrote:
Hello
2013/7/30 <arun.rh@gmail.com>:
The following bug has been logged on the website:
Bug reference: 8345
Logged by: Arun Kumar
Email address: arun.rh@gmail.com
PostgreSQL version: Unsupported/Unknown
Operating system: Linux kernel 2.6.29
Description:Currently we have ported PostGRE SQL database on to the Linux kernel
2.6.29
with Motorolla coldfire cross platform.
Version of PostgreSQL = 7.4.3.This version is very old, and there are exists lot of upgrade of
7.4.3, so please upgrade to last 7.4 versionhttp://www.postgresql.org/ftp/source/v7.4.30/ is probably last.
Yeah, also 7.4 is EOL for 4~5 years, so it is not anymore supported by the
community. By the way, a crash could have been caused for many reasons,
including failures at the filesystem level, or hardware level. So if you
first do not provide more information about the circumstances of the crash,
it will be difficult to make a diagnostic of your problems.
As Pavel said, also please consider upgrading.
--
Michael