From jaruwan@gits.net.th Mon Jan 29 11:44:42 2001 Received: from edison.gits.net.th (edison.gits.net.th [164.115.2.130]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f0TBigq78132; Mon, 29 Jan 2001 06:44:42 -0500 (EST) (envelope-from jaruwan@gits.net.th) Received: from wan ([203.150.154.109]) by edison.gits.net.th (8.10.1/8.10.1) with SMTP id f0TBiml20977; Mon, 29 Jan 2001 18:44:48 +0700 (GMT) Message-ID: <00d501c089e9$8c63a620$6d9a96cb@ntl> From: "Jaruwan Laongmal" To: , Subject: Emergency case: Postgres problems Date: Mon, 29 Jan 2001 18:49:32 +0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00D2_01C08A24.37E0A9A0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 X-Archive-Number: 200101/1282 X-Sequence-Number: 4042 This is a multi-part message in MIME format. ------=_NextPart_000_00D2_01C08A24.37E0A9A0 Content-Type: text/plain; charset="windows-874" Content-Transfer-Encoding: quoted-printable Dear Sir, I will highly appreciated if anyone could inform me how to solve the follo= wing problems in Postgres. Specifically, sometimes there are the following messages informed by postg= res. ------------------------------------------------ NOTICE: Message from PostgreSQL backend: The Postmaster has informed me that some other backend died abnorma= lly and possibly corrupted shared memory. I have rolled back the current transaction and am going to terminat= e 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=20 PS. The Postgres version is 7.0.0 run on Red Hat Linux 7.1 ------=_NextPart_000_00D2_01C08A24.37E0A9A0 Content-Type: text/html; charset="windows-874" Content-Transfer-Encoding: quoted-printable
Dear Sir,
 
I  will highly appreciated if anyone= could=20 inform me how to solve the following problems in Postgres.
Specifically, sometimes there  are the following m= essages=20 informed by postgres.
 
------------------------------------------------
NOTICE:  Message from PostgreSQL=20 backend:
        The Postmaster has= =20 informed me that some other backend died abnormally and possibly corrupted= =20 shared memory.
        I have rolled = back=20 the current transaction and am going to terminate your database system=20 connection and exit.
        Please= =20 reconnect to the database system and repeat your query.
pqReadData() --= =20 backend closed the channel=20 unexpectedly.
        This probably m= eans=20 the backend terminated abnormally
      &n= bsp;=20 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 Linu= x=20 7.1
 
 
------=_NextPart_000_00D2_01C08A24.37E0A9A0-- From janwieck@Yahoo.com Mon Jan 29 19:23:21 2001 Received: from smtp1.mail.yahoo.com (smtp1.mail.yahoo.com [128.11.69.60]) by mail.postgresql.org (8.11.1/8.11.1) with SMTP id f0TJNLq25197 for ; Mon, 29 Jan 2001 14:23:21 -0500 (EST) (envelope-from janwieck@yahoo.com) Received: from j13.us.greatbridge.com (HELO jupiter.greatbridge.com) (216.54.52.153) by smtp.mail.vip.suc.yahoo.com with SMTP; 29 Jan 2001 19:23:19 -0000 X-Apparently-From: Received: (from janwieck@localhost) by jupiter.greatbridge.com (8.9.3/8.9.3) id OAA04522; Mon, 29 Jan 2001 14:33:13 -0500 From: Jan Wieck Message-Id: <200101291933.OAA04522@jupiter.greatbridge.com> Subject: Re: Emergency case: Postgres problems In-Reply-To: <00d501c089e9$8c63a620$6d9a96cb@ntl> from Jaruwan Laongmal at "Jan 29, 2001 06:49:32 pm" To: Jaruwan Laongmal Date: Mon, 29 Jan 2001 14:33:13 -0500 (EST) CC: pgsql-hackers@postgresql.org, pgsql-sql@postgresql.org X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archive-Number: 200101/1314 X-Sequence-Number: 4079 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