From: Jan Wieck <janwieck@Yahoo.com>
To: Jaruwan Laongmal <jaruwan@gits.net.th>
Cc: pgsql-hackers@postgresql.org
Cc: pgsql-sql@postgresql.org
Subject: Re: Emergency case: Postgres problems
Date: Mon, 29 Jan 2001 14:33:13 -0500 (EST)
Message-ID: <200101291933.OAA04522@jupiter.greatbridge.com> (raw)
In-Reply-To: <00d501c089e9$8c63a620$6d9a96cb@ntl>
Jaruwan Laongmal wrote:
[Charset windows-874 unsupported, skipping...]
> Dear Sir,
>
> I will highly appreciated if anyone could inform me how to solve the following problems in Postgres.
> Specifically, sometimes there are the following messages informed by postgres.
>
> ------------------------------------------------
> NOTICE: Message from PostgreSQL backend:
> The Postmaster has informed me that some other backend died abnormally and possibly corrupted shared memory.
> I have rolled back the current transaction and am going to terminate your database system connection and exit.
> Please reconnect to the database system and repeat your query.
> pqReadData() -- backend closed the channel unexpectedly.
> This probably means the backend terminated abnormally
> before or while processing the request.
> ------------------------------------------------
>
> Thank you so much for your concern
>
> Jaruwan
>
>
> PS. The Postgres version is 7.0.0 run on Red Hat Linux 7.1
Upgrade to 7.0.3, which is the latest bugfix release of the
7.0 version. There is a good chance that the error causing
your database process to dump core is fixed in it.
If the problem persists after, you should look for the core
file in your database directory, use gdb to get a stack
backtrace and post that information to the list again.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck@Yahoo.com #
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: janwieck@Yahoo.com, jaruwan@gits.net.th, pgsql-hackers@postgresql.org
Subject: Re: Emergency case: Postgres problems
In-Reply-To: <200101291933.OAA04522@jupiter.greatbridge.com>
References: <00d501c089e9$8c63a620$6d9a96cb@ntl> <200101291933.OAA04522@jupiter.greatbridge.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox