pg.ddx.io pgsql-sql@postgresql.org mailing list archive
help / color / mirror / Atom feedEmergency case: Postgres problems
2+ messages / 2 participants
[nested] [flat]
* Emergency case: Postgres problems
@ 2001-01-29 11:49 Jaruwan Laongmal <jaruwan@gits.net.th>
2001-01-29 19:33 ` Re: Emergency case: Postgres problems Jan Wieck <janwieck@Yahoo.com>
0 siblings, 1 reply; 2+ messages in thread
From: Jaruwan Laongmal @ 2001-01-29 11:49 UTC (permalink / raw)
To: pgsql-hackers@postgresql.org; pgsql-sql
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
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: Emergency case: Postgres problems
2001-01-29 11:49 Emergency case: Postgres problems Jaruwan Laongmal <jaruwan@gits.net.th>
@ 2001-01-29 19:33 ` Jan Wieck <janwieck@Yahoo.com>
0 siblings, 0 replies; 2+ messages in thread
From: Jan Wieck @ 2001-01-29 19:33 UTC (permalink / raw)
To: Jaruwan Laongmal <jaruwan@gits.net.th>; +Cc: pgsql-hackers@postgresql.org; pgsql-sql
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
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2001-01-29 19:33 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2001-01-29 11:49 Emergency case: Postgres problems Jaruwan Laongmal <jaruwan@gits.net.th>
2001-01-29 19:33 ` Jan Wieck <janwieck@Yahoo.com>
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